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

add github action to build and deploy the dev CD/service #1021

Merged
merged 8 commits into from
Jan 31, 2024

Conversation

elrayle
Copy link
Collaborator

@elrayle elrayle commented Jan 12, 2024

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

@elrayle elrayle marked this pull request as draft January 16, 2024 20:42
@elrayle elrayle force-pushed the elr/gh-action-dev-deploy branch 14 times, most recently from 8baeaae to 75c167f Compare January 23, 2024 13:54
@elrayle elrayle force-pushed the elr/gh-action-dev-deploy branch from 31298b2 to 4334f74 Compare January 24, 2024 14:56
@elrayle elrayle marked this pull request as ready for review January 24, 2024 15:05
@elrayle elrayle requested a review from qtomlinson January 26, 2024 15:16
Copy link
Collaborator

@qtomlinson qtomlinson left a 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.

.github/workflows/build_and_deploy_dev.yml Outdated Show resolved Hide resolved
routes/index.js Show resolved Hide resolved
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.
@elrayle elrayle force-pushed the elr/gh-action-dev-deploy branch from 4334f74 to 662c166 Compare January 30, 2024 21:29
@elrayle elrayle force-pushed the elr/gh-action-dev-deploy branch from 0af3f1b to 6aac9c9 Compare January 31, 2024 14:32
@elrayle
Copy link
Collaborator Author

elrayle commented Jan 31, 2024

@qtomlinson Thanks for the review. I've updated the code in the last two commits to address your comments.

@elrayle elrayle force-pushed the elr/gh-action-dev-deploy branch from e4f6248 to 2b273f6 Compare January 31, 2024 18:52
Removes the temporary trigger to deploy on the PR branch.
Copy link
Collaborator

@qtomlinson qtomlinson left a 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.

.github/workflows/build_and_deploy_dev.yml Outdated Show resolved Hide resolved
.github/workflows/build_and_deploy_dev.yml Outdated Show resolved Hide resolved
@elrayle
Copy link
Collaborator Author

elrayle commented Jan 31, 2024

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.

@elrayle elrayle merged commit efeed96 into master Jan 31, 2024
2 checks passed
@elrayle elrayle deleted the elr/gh-action-dev-deploy branch January 31, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants