This message was deleted.
# ask-marvin
s
This message was deleted.
m
To pass specific fields such as the container and folder while initializing a Prefect project with the Azure recipe, you typically use the
prefect init --recipe
command. Here's how you can do it for both Prefect 2.x and 3.x versions: ### For Prefect 2.x: To run the
azure
recipe and specify fields, you should run:
Copy code
sh
prefect init --recipe azure
During the initialization, you’ll be prompted to enter values for parameters such as container and folder. Based on the documentation: #### Example parameters often include: - container: The name of the Azure Blob Storage container. - folder: The folder within the container where your data and flows are stored. Here’s a basic example:
Copy code
sh
prefect init --recipe azure
Then follow the prompts to specify: 1. Enter the container name when prompted:
Copy code
sh
   Enter Azure Blob Storage container name: my-container
2. Enter the folder name when prompted:
Copy code
sh
   Enter folder name within the container: my-folder
### For Prefect 3.x: The
prefect init --recipe azure
command works similarly in Prefect 3.x. If you face any issue, make sure that there is no bug associated with that version. For instance, issue 9962 reported a related bug, but following the typical flow should still prompt you for necessary fields. Links: 1. Prefect Recipes Overview 2. Azure Integration in Prefect Let me know if you need any further assistance!
It looks like passing parameters directly via the command line for the
prefect init --recipe
command is not currently documented in the existing Prefect 2.x or 3.x documentation. Here is some relevant information: ### Prefect 2.x Documentation: There is no specific section that explicitly handles passing fields directly as arguments in the
prefect init --recipe azure
command. Most parameters are expected to be input interactively. ### Prefect 3.x Documentation: Similar to 2.x, there are no direct mentions of passing parameters via command line arguments for
prefect init --recipe azure
, suggesting you might need to follow the interactive prompts approach. ### Attempt to Find Solutions on GitHub Issues: A quick search through GitHub issues also did not yield any conclusive solution for bypassing the prompt entirely via command line. ### Alternative Approach (Default Configuration): Given this information, you might need to resort to using the default configuration and then modify the
prefect.yaml
file or deployment configuration file post initialization. ### Sample Workflow: 1. Initialize the recipe:
Copy code
sh
   prefect init --recipe azure
2. Modify the configuration file: After initialization, update the
prefect.yaml
or relevant files with your specific container and folder settings. ### Helpful Links: 1. Prefect Recipes Overview 2. Deploying with Azure 3. GitHub Prefect Issues Currently, this may require a bit more manual work until this feature is possibly integrated in future updates. If this functionality is critical for your use case, I recommend creating an issue or feature request on Prefect's GitHub to make the development team aware of this need.