-
Notifications
You must be signed in to change notification settings - Fork 4
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
AV-90385 Azure cluster updates #240
Open
PaulomeeCb
wants to merge
20
commits into
main
Choose a base branch
from
AV-90385_Azure_cluster_changes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+820
−27
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
Talina06
reviewed
Nov 12, 2024
PaulomeeCb
changed the title
AV-90385 Azure cluster - ultra and premium chagNes
AV-90385 Azure cluster - ultra and premium changes
Nov 13, 2024
PaulomeeCb
changed the title
AV-90385 Azure cluster - ultra and premium changes
AV-90385 Azure cluster - ultra and premium Documentation update
Nov 13, 2024
PaulomeeCb
changed the title
AV-90385 Azure cluster - ultra and premium Documentation update
AV-90385 Azure cluster - premium changes
Nov 15, 2024
PaulomeeCb
changed the title
AV-90385 Azure cluster - premium changes
AV-90385 Azure cluster updates
Nov 15, 2024
SaicharanCB
previously approved these changes
Nov 26, 2024
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.
+1
tested here http://172.23.121.80/job/terraform-test/789/
SaicharanCB
approved these changes
Nov 27, 2024
l0n3star
requested changes
Nov 27, 2024
l0n3star
approved these changes
Dec 2, 2024
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.
Jira
Description
In this PR, I am doing the following -
Update will read the plan and if it finds the default values for iops and storage in premium-type disks, then it will not throw an error, else if the user explicitly adds some other values, it throws an error. This will be caught in terraform before passing to open-api.
Create will not allow passing any values for iops and storage for premium-type disks, and this is caught at terraform before passing to open-api. Hence, the error is thrown after terraform apply from terraform.
Updated the README and example files for more clarity on Premium and ultra type disks for azure clusters.
All tests documented here- https://docs.google.com/document/d/1oIYkLpuiGcO_05Pkon0JIUYt-VmxojHCKWn4AX1F7oY/edit?tab=t.0
Type of Change
Manual Testing Approach
All tests documented here- https://docs.google.com/document/d/1oIYkLpuiGcO_05Pkon0JIUYt-VmxojHCKWn4AX1F7oY/edit?tab=t.0
Deploying Ultra-type Azure cluster -
Deployed successfully -
Updating Ultra-type Azure cluster-
~ update in-place
Updated-
Correct error thrown when wrong values added-
Deploying Premium-type Azure cluster-
Testing added to the Readme
Throws correct error when Iops and Storage is added in payload for Create-
Update is successful-
How was this change tested and do you have evidence? (REQUIRED: Select at least 1)
Testing
Will add ss/ recording.
Testing
Required Checklist:
Further comments