@Marvin How can I pass a secret parameter to a subflow without having it passed to the Prefect Cloud?

To pass a secret parameter to a subflow without having it passed to Prefect Cloud, you have a few options: 1. Flow and Task Parameters: Flow parameter values are stored by Prefect in the database, while task parameter values are not. Therefore, you might prefer to use task parameters for sensitive information. This does mean you would need to ensure that the specific piece of data you wish to keep secret is only used within task scopes. 2. Blocks: Use Prefect Blocks to store configurations and interfaces to external systems securely. Each block document is encrypted uniquely, and Prefect only encrypts the data before storing it, which means it could be a secure way to manage secrets without sending them directly through the Cloud. Keep in mind that it's crucial to avoid logging sensitive values. If necessary, disable logging for those specific tasks or subflows handling the secret parameters. Please note that you should confirm the current behavior with the latest Prefect documentation or support forums to ensure that no changes have occurred which might affect this advice. Reference links: - Prefect Security - Prefect Troubleshooting Guide Would you like to search GitHub issues for real-world instances of users handling secret parameters?