-
Notifications
You must be signed in to change notification settings - Fork 3.5k
{AKS} az aks get-versions: get-versions using newer backend api
#26702
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
Changes from all commits
9d2c82a
ea91261
08f469e
c9389cf
d1d88c7
553ced1
b3bf3df
2dc56aa
ec68529
5c57afa
46a0606
23018c8
c8690ce
82a8f1b
d9a04ff
dad85cf
e15c61c
9df20ec
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -173,7 +173,7 @@ def test_aks_create_default_setting(self, resource_group, resource_group_locatio | |
| 'dns_name_prefix': self.create_random_name('cliaksdns', 16), | ||
| 'ssh_key_value': self.generate_ssh_keys().replace('\\', '\\\\'), | ||
| 'location': resource_group_location, | ||
| 'service_principal': _process_sp_name(sp_name), | ||
| 'service_principal': sp_name, | ||
| 'client_secret': sp_password, | ||
| 'resource_type': 'Microsoft.ContainerService/ManagedClusters' | ||
| }) | ||
|
|
@@ -266,7 +266,7 @@ def test_aks_nodepool_create_scale_delete(self, resource_group, resource_group_l | |
| 'dns_name_prefix': self.create_random_name('cliaksdns', 16), | ||
| 'ssh_key_value': self.generate_ssh_keys().replace('\\', '\\\\'), | ||
| 'location': resource_group_location, | ||
| 'service_principal': _process_sp_name(sp_name), | ||
| 'service_principal': sp_name, | ||
| 'client_secret': sp_password, | ||
| 'resource_type': 'Microsoft.ContainerService/ManagedClusters', | ||
| 'tags': tags, | ||
|
|
@@ -477,7 +477,7 @@ def generate_ppg_id(self, resource_group, location): | |
| def _get_versions(self, location): | ||
| """Return the previous and current Kubernetes minor release versions, such as ("1.11.6", "1.12.4").""" | ||
| versions = self.cmd( | ||
| "az aks get-versions -l westus2 --query 'orchestrators[].orchestratorVersion'").get_output_in_json() | ||
| "az aks get-versions -l westus2 --query 'values[*].patchVersions.keys(@)[]'").get_output_in_json() | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this change necessary? To me, the recording file is not changed, so I guess without the change, the test could pass.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The unit test that has _get_versions is test_aks_create_service_no_wait which is live_only.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @haitch can you confirm?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @FumingZhang , I think I just did a search of "get-versions", and update here. And, I am expecting this need to be updated as well, unless the hybrid test is something different.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK, as the recording file for the hybrid version is not updated, I thought we may keep the test case unchanged. But CI has passed, shouldn't block the change. |
||
| # sort by semantic version, from newest to oldest | ||
| versions = sorted(versions, key=version_to_tuple, reverse=True) | ||
| upgrade_version = versions[0] | ||
|
|
||
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.
May I ask if this modification will change the output logic and cause a breaking change to customers?
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 is not a breaking change. Customers will not experience any interruptions.