Dynamic Service SD Creation #551
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
updated new parameter to latest_deployed_github_repo_commit updated update_data_stores_and_sd_files script to use the latest_deployed_github_repo_commit to get diff from that commit only recreate SD files if mapx files have changed since last commit used
shawncrawley
previously approved these changes
Sep 28, 2023
|
Wow, this is cool! Way to go. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently when we do a deploy, all service SD files are recreated and that causes all services to be republished. With over 100 services now, that puts a strain on the EGIS systems to do all that republishing so close together.
This PR aims to reduce the service republishing to only the services that need it. The github commit that was used in a deploy is stored in the AWS parameter store. This github commit is then used in the next deploy so that changes between the latest deploy and the current deploy can be tracked. Any mapx files that have been changed since that deployment will have their SD files recreated and thus be republished.