Using azd pipeline config with multiple environments or multiple projects #3585
-
|
How can I use It looks like no matter what environment I select; the same secrets and variables are created in GitHub. I would like to use different Azure subscriptions / resource groups / ... with different environments. I tried using GitHub environments, but secrets / variables are not stored within GitHub environments. What about having multiple projects in one GitHub repository? How can I use |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hello @christiannagel. There's a CI/CD model which might help you, but it less common. You can ask azd to create one git remote per azd-environment (using --remote-name flag), which would get you with one gh-repository per azd-environment. Then, depending on which remote you push your local changes is where CI/CD runs. We have an open discussion around adding support for CI/CD environments here: #2373 |
Beta Was this translation helpful? Give feedback.
Hello @christiannagel.
Up to now,
azd pipeline configsupports setting up only one azd-environment per repository. So, even if you have just one azd project locally but with more than one azd-environment, azd can only set one azd-env for CI/CD.There's a CI/CD model which might help you, but it less common. You can ask azd to create one git remote per azd-environment (using --remote-name flag), which would get you with one gh-repository per azd-environment. Then, depending on which remote you push your local changes is where CI/CD runs.
We have an open discussion around adding support for CI/CD environments here: #2373