-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
{AKS} Add support for option --aks-custom-headers
to some aks commands
#6430
{AKS} Add support for option --aks-custom-headers
to some aks commands
#6430
Conversation
Hi @FumingZhang, |
AKS |
00c47df
to
a6bed07
Compare
--aks-custom-headers
to some aks commands
|
||
@AllowLargeResponse() | ||
@AKSCustomResourceGroupPreparer(random_name_length=17, name_prefix='clitest', location='eastus', preserve_default_location=True) | ||
def test_aks_create_with_custom_headers(self, resource_group, resource_group_location): |
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.
Queued live test to validate the change.
[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=67287&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
{AKS} Add support for option
--aks-custom-headers
to the following aks commands, feature request from aurora team.Fix recordings as the inherited command
az aks get-version
bumped API version yesterday (by PR #26718). Overwrite the implementation in aks-preview, so the issue won't happen again.General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json
.