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.
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
chore: Updates examples and documentation in resource and data source with new ISS attributes and structure #2438
chore: Updates examples and documentation in resource and data source with new ISS attributes and structure #2438
Changes from 6 commits
0a06afb
d56cb4d
2a8f83f
7010353
b68ac09
f015f3f
d68d375
5a9b9b4
46bc7dc
ae0b4ec
96aabae
f8e9376
957ab57
c5fd897
739ed86
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same for
# shard 2 - zone n2
-># shard 4 - zone n2
Do you think this would make it more clear? At the end the configuration is defining 4 shards, 2 in each zone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think since the zone is mentioned alongside, this should not be updated to shard 3 & 4. In the current way it seems clear that it's 2 shards in each zone
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If
use_replication_spec_per_shard = true
we still populate this root value, so believe this additional comment is not needed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was added to address this point in the ticket
Mention impact on root disk_size_gb computed value if new flag is used.
Is there anything we should mention on this? If not, I can remove the additional commentThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad for not updating that mention, after #2405 logic was added to always populate at the root level to avoid breaking changes in the resource, and having that implementation in place it was added to the data source as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
discussed offline, removed