Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azd pipeline config support for different branches #2040

Closed
weikanglim opened this issue Apr 27, 2023 · 3 comments · Fixed by #2468
Closed

azd pipeline config support for different branches #2040

weikanglim opened this issue Apr 27, 2023 · 3 comments · Fixed by #2468
Assignees

Comments

@weikanglim
Copy link
Contributor

As a user, I should be able to run azd pipeline config to configure the Azure connection for different branches. The branch-specific behavior may be specific to federated credentials.

I want to be able to do this to configure CD for my mainline branch that is not main, or potentially other release servicing branches.

See original comment here

@ghost ghost added the needs-triage For new issues label Apr 27, 2023
@ghost ghost removed the needs-triage For new issues label Apr 28, 2023
@vhvb1989
Copy link
Member

My 2 cents:
Let azd to be an example for how to set up a reference pipeline, but not as the tool you need to use for setting up all your pipelines.
In this case, for example, supporting multiple branches would require to create a group of secrets per branch so I could use azd for 3 different branches and each pipeline could have its own env values (secrets). This complicates things IMO.

@jongio
Copy link
Member

jongio commented May 15, 2023

I would like azd to help me create the FIC for the branches I want the action to run on. It could look at my default gh action, see which branches I have listed there, and then create FICs for each branch. As it is now, I need to figure out how to create my own FIC.

@wbreza
Copy link
Contributor

wbreza commented Jun 29, 2023

@weikanglim / @jongio - I believe this PR #2468 should solve the concern / issue here.

@wbreza wbreza self-assigned this Jun 29, 2023
@wbreza wbreza added this to the July 2023 - 1.1.0 milestone Jun 29, 2023
wbreza added a commit that referenced this issue Jul 6, 2023
…ation (#2468)

Fixes #2428, #2040

Includes the current git branch name when setting up federated credentials for GitHub.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants