-
Notifications
You must be signed in to change notification settings - Fork 6
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
AWS CodePipeline setup #204
Merged
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
hamzajaved-csiro
force-pushed
the
ci/code-pipeline
branch
4 times, most recently
from
April 26, 2024 01:37
d3c90e7
to
9c501b3
Compare
hamzajaved-csiro
force-pushed
the
ci/code-pipeline
branch
6 times, most recently
from
May 7, 2024 05:04
1e6e8a6
to
dc02d24
Compare
Most of the pipeline updates done for alerts also some structural changes and work to keep things consistent
Also a refactor so that environment vars are only passed to a code build project through the pipeline. It was arbitrary split between code pipeline and code build which makes it hard to see what vars we have
Also clean up and standardise where env vars are passed to code pipeline
* split components * commit build changes * commit build changes * repo and tagging changes * upgrade build containers * remove base stack name from pipeline * remove unused vars * remove the old containers component * pass secret to the build component * import DB endpoints * update DB stack name to point ot another branch * correct var name * tweak secrets vars * fix output ref * simplify aws account id retrieval * revert to older ubuntu * use default python in codebuild containers * tag Docker image with build number * remove the ID from the secret name * add tag to push as well * pass aws account into deploy buildspec * simplify pipeline params * Add latest tag * Add latest tag in deploy spec * Add latest tag in deploy spec * remove stack name * Update port number in ingress deployment * Update ingress in helm * Update ingress in helm * Update target port * Update target port * Update target port * Add SSL certificate and rds external name service * Add external dns creation * Add hostname * Fix config.ini * Delete old pipeline and update helm charts --------- Co-authored-by: Hamza Javed <[email protected]>
hamzajaved-csiro
force-pushed
the
ci/code-pipeline
branch
from
July 10, 2024 03:16
400d120
to
6956b01
Compare
Merging into develop branch to redeploy infrastucture |
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.
No description provided.