-
Notifications
You must be signed in to change notification settings - Fork 113
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
support max shard configuration via patch #8048
Merged
kalroy
merged 7 commits into
main
from
CHEF-3647-max-shard-configuration-should-be-configurable-in-automate-ha-opensearch-config
Jul 24, 2023
Merged
support max shard configuration via patch #8048
kalroy
merged 7 commits into
main
from
CHEF-3647-max-shard-configuration-should-be-configurable-in-automate-ha-opensearch-config
Jul 24, 2023
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
✅ Deploy Preview for chef-automate ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
shaik80
requested review from
ArvinthC3000 and
sandhi18
and removed request for
ArvinthC3000
July 10, 2023 12:53
github-actions
bot
added
the
documentation
Anything related to the Automate docs.
label
Jul 12, 2023
shaik80
changed the title
[WIP] support max shard configuration via patch
support max shard configuration via patch
Jul 12, 2023
jayvikramsharma1
approved these changes
Jul 12, 2023
punitmundra
approved these changes
Jul 13, 2023
terraform/a2ha-terraform/modules/opensearch/templates/opensearch_user.toml.tpl
Outdated
Show resolved
Hide resolved
vivekshankar1
approved these changes
Jul 13, 2023
vivek-yadav
approved these changes
Jul 13, 2023
atultherajput
approved these changes
Jul 13, 2023
shaik80
changed the title
support max shard configuration via patch
[WIP] support max shard configuration via patch
Jul 18, 2023
shaik80
force-pushed
the
CHEF-3647-max-shard-configuration-should-be-configurable-in-automate-ha-opensearch-config
branch
from
July 21, 2023 11:43
925bfeb
to
cc95bbd
Compare
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
Signed-off-by: shaik80 <shaik.mudassir@progress.com>
shaik80
force-pushed
the
CHEF-3647-max-shard-configuration-should-be-configurable-in-automate-ha-opensearch-config
branch
from
July 21, 2023 11:44
cc95bbd
to
0d8624e
Compare
shaik80
changed the title
[WIP] support max shard configuration via patch
support max shard configuration via patch
Jul 21, 2023
SonarQube Quality Gate |
vivekshankar1
approved these changes
Jul 21, 2023
kalroy
deleted the
CHEF-3647-max-shard-configuration-should-be-configurable-in-automate-ha-opensearch-config
branch
July 24, 2023 04:11
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?
we need to support max_shard_per_node via patch command
⛓️ Related Resources
https://chefio.atlassian.net/browse/CHEF-3647
👍 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 spell
in 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
Demo Video : max_shard_per_node.mp4