Migrate helm agent to 3.x.x #479
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
added 2 commits
February 2, 2024 15:14
- Migrate to use litmusctl 1.2.0
- Updated field to use Infrastructure instead of agent
- Include new parameters in the parameters/configmap needed for 3.X
- Removed unused line "prepareInfraSecret"
Signed-off-by: Calvin Audier <[email protected]>
- Execute "go mod tidy" - Add comment to precise litmusctl version Signed-off-by: Calvin Audier <[email protected]>
Jonsy13
requested review from
ispeakc0de,
Jonsy13,
SarthakJain26 and
Saranya-jena
Saranya-jena
approved these changes
Feb 22, 2024
Jonsy13
approved these changes
Feb 23, 2024
SarthakJain26
approved these changes
Feb 23, 2024
|
LGTM, Thanks @Calvinaud for contribution!! |
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.
What this PR does / why we need it:
Migrate litmus-helm-agent to use version 3.x.x of litmus.
Upgrading to litmusctl 1.2.0.
Which issue this PR fixes
fixes #450
Special notes for your reviewer:
Should we change the change of the
litmus-helm-agenttolitmus-helm-infra?