Remvoing config patch for old configs in upgrade and add/remove node #8296
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
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
ArvinthC3000
requested review from
vivek-yadav,
jayvikramsharma1,
punitmundra,
karunesh-tech and
bvtejaswi
👷 Deploy Preview for chef-automate processing.
|
punitmundra
requested changes
Nov 20, 2023
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
punitmundra
approved these changes
Nov 20, 2023
punitmundra
approved these changes
Nov 21, 2023
bvtejaswi
approved these changes
Nov 21, 2023
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
|
SonarQube Quality Gate
|
anees-progress
pushed a commit
that referenced
this pull request
Nov 30, 2023
…8296) * Remoing config patch for old configs in upgrade and add/remove node Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Trigger build Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Stash for save and sync config for upgrade flow Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Removing stash Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> --------- Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
anees-progress
pushed a commit
that referenced
this pull request
Nov 30, 2023
…8296) * Remoing config patch for old configs in upgrade and add/remove node Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Trigger build Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Stash for save and sync config for upgrade flow Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Removing stash Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> --------- Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
swatiganesh
pushed a commit
that referenced
this pull request
Apr 16, 2024
…8296) * Remoing config patch for old configs in upgrade and add/remove node Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Trigger build Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Stash for save and sync config for upgrade flow Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> * Removing stash Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com> --------- Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
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.
🔩 Description: What code changed, and why?
When user upgrade the bundle to latest, some configuration belongs to Automate config which are updated are reverting back to initial values. In this PR, that is addressed
⛓️ Related Resources
Jira ticket: https://chefio.atlassian.net/browse/CHEF-8418
👍 Definition of Done
👟 How to Build and Test the Change
✅ Checklist
All PRs must tick these:
With occasional exceptions, all PRs from Progress employees must tick these:
make spellin any component directory)All PRs from Progress employees should tick these if appropriate:
Please add a note next to any checkbox above if you are NOT ticking it.
📷 Screenshots, if applicable
In the below screenshot, when the deployment done, the original base path highlighted would be "elasticsearch", which lated updated to "opensearch".
After upgrade, the same value is intact
Screenshot