chore: Remove secure repo and fetch secrets from AWS for analytics je… #1681
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
|
@HassanJaveed84 We are in the process of eliminating the secure repository from Jenkins and transitioning to fetching secrets from AWS. I've implemented adjustments for DE jobs that rely on the "user-retirement-secure" repository. These changes have been tested on jobs located in tools-Jenkins (PR for that change). I would appreciate your review of these modifications. |
syedimranhassan
force-pushed
the
ihassan/CLOUDSEC-34_fetch_secret_aws_analytics_jenkins
branch
from
a5695d7 to
db1fce6
Compare
syedimranhassan
force-pushed
the
ihassan/CLOUDSEC-34_fetch_secret_aws_analytics_jenkins
branch
from
b6b463f to
d5655cc
Compare
syedimranhassan
deleted the
ihassan/CLOUDSEC-34_fetch_secret_aws_analytics_jenkins
branch
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.
…nkins jobs