@Marvin What is the status of

DatabaseCredentials

? It seems like the github project for

prefect_sqlalchemy

is deprecated but the integration inside Prefect (

prefect[sqlalchemy]

) does not seems to support it. What is the proper way to read from a

Database Credentials

block? It it not marked as deprecated on the managed prefect (prefect.cloud)

The

DatabaseCredentials

block is still supported in Prefect, despite the deprecation of the

prefect_sqlalchemy

GitHub project. The integration for working with databases using Prefect is now handled through the

prefect-sqlalchemy

package, which you can install and use with Prefect. Here's how you can read from a

DatabaseCredentials

block: 1. Installation: Ensure you have the

prefect-sqlalchemy

package installed. You can do this by running:

bash
   pip install prefect-sqlalchemy

2. Registering Blocks: After installation, register the block types in the

prefect-sqlalchemy

module to make them available for use. 3. Using the Block: You can save credentials to a block and then load the saved block that holds your credentials. Here's a basic example:

python
   from prefect_sqlalchemy import DatabaseCredentials

   # Load your credentials block
   credentials_block = DatabaseCredentials.load("my-database-credentials")

   # Use credentials block in your flow

For more information, you can refer to the Prefect SQLAlchemy Integration Documentation. Additionally, the

DatabaseCredentials

type is used in the Prefect flows as shown in this GitHub issue example: Delayed flow/task start. If you're using Prefect Cloud, the

DatabaseCredentials

block is not marked as deprecated, and you should be able to use it as described.

@Marvin there are no implementation of

DatabaseCredentials

inside https://github.com/PrefectHQ/prefect (and in particular in

<https://github.com/PrefectHQ/prefect/tree/main/src/integrations/prefect-sqlalchemy>

) The project https://github.com/PrefectHQ/prefect-sqlalchemy is archived since april 2024

The

DatabaseCredentials

block was indeed part of the

prefect-sqlalchemy

package, which has been archived since April 2024. This means that while the block was available for use in Prefect flows, its future support and updates are uncertain due to the archiving of the repository. Given this situation, here's what you can do: 1. Existing Usage: If you have existing workflows using

DatabaseCredentials

, they may continue to work as expected, but be aware that there might be no future updates or support for this block. 2. Alternative Solutions: Consider using alternative methods for managing database connections. You might directly use SQLAlchemy or other database connection libraries in your Prefect flows. Prefect's flexibility allows you to integrate any Python library, so you can manage connections and credentials programmatically. 3. Monitor Updates: Keep an eye on Prefect's official announcements or GitHub repositories for any new integrations or changes regarding database connection management. For more details on the archived repository, you can view the discussions and issues on the prefect-sqlalchemy GitHub page. If you need further guidance on setting up database connections manually in your flows, I can help with that as well.

hi @Gaël Grosch - as mentioned on the readme

Active development of this project has moved within PrefectHQ/prefect. The code can be found here and documentation here. Please open issues and PRs against PrefectHQ/prefect instead of this repository.

prefect-sqlalchemy

just lives in

prefecthq/prefect

now what are you trying to do? this is usually the block that's most useful directly

Hi @Nate, thanks for the reply, I am using psycopg3 and not sqlalchemy so I wanted to only get the credentials without all the logic to get a connector I do not need. In the end I used a connection info string as secret to work around the disapperance of

DatabaseCredentials