-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feat: infra pipeline tag trigger #310
Conversation
108e642
to
d1ceddf
Compare
Need to look at this a little closer - specifically the |
d1ceddf
to
da549aa
Compare
# service connection | ||
environmentServiceNameAzureRM: deployer | ||
# the plan is done as part of the apply (below), so don't bother doing it twice | ||
condition: notIn(variables['Build.SourceBranchName'], 'dev', 'test', 'prod') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We no longer need a condition on the terraform plan
step because it should always run.
second stage requires environment with approval check. change 'terraform plan' step to always run.
da549aa
to
3610f01
Compare
This is ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great @angela-tran!! Huge props for making so much progress in a short amount of time 👍
Closes #284
This PR makes it possible for our existing pipeline in MST's DevOps to be triggered by pushing a git tag.
The only thing not defined in code here is the Environment which needs to be created manually and configured manually.