-
Notifications
You must be signed in to change notification settings - Fork 41
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
add github action to build and deploy the dev CD/service #1021
Conversation
8baeaae
to
75c167f
Compare
31298b2
to
4334f74
Compare
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.
Nice work! Really appreciated the background information in the PR.
The variables defined in the `env:` section allow this script to be used in other contexts with minimal modification, primarily modifying just the environment variables. _NOTE: SEMVER is a place holder. A version is note assigned for dev deploys, but will be used in production deploys._ Change the file used for building to Dockerfile. The DevDockerfile is for localhost deploy only for dev testing.
4334f74
to
662c166
Compare
0af3f1b
to
6aac9c9
Compare
@qtomlinson Thanks for the review. I've updated the code in the last two commits to address your comments. |
e4f6248
to
2b273f6
Compare
Removes the temporary trigger to deploy on the PR branch.
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.
Great documentation! Minor fixes see comments.
I've been going back and forth on whether in production, there should be sha and semver tags or just semver tag. It doesn't have to be resolved for this PR, but I'd like to get opinions on this. Theoretically, if you have the semver, you can get the sha from the release tag in GitHub. If we choose to only have a single tag for both dev and prod, it simplifies the action. |
Description
This PR adds a GitHub action to perform the deploy of service to the dev service app in Azure. To support debugging, it also adds the sha of the current deploy to the status endpoint.
NOTE: As part of this work, Azure auth credentials were created following this documentation.
Follow-on Work