-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
SDK code for shared gallery, image features and blob as source #19472
Conversation
…ofile and shared gallery
This reverts commit 051be54.
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them. In order to bootstrap pipelines for a new service, please perform following steps: For data-plane/track 2 SDKs Issue the following command as a pull request comment:
For track 1 management-plane SDKsPlease open a separate PR and to your service SDK path in this file. Once that PR has been merged, you can re-run the pipeline to trigger the verification. |
* Creating nuget package for blob as source (Azure#20127) * save the auto-generation work * add gallery application version update auto-generation * nit, add new line * update record json * update record json and add new tests for caps gallery with sharing profile and shared gallery * save work for gallery with sharing profile, caps side test * update blob as source code * uncheck shared gallery test which can not run right now * save * save * add shared gallery tests * generate files again * Revert "generate files again" This reverts commit 051be54. * update gallery * revert unnecessary change * update examples * Update Microsoft.Azure.Management.Compute.csproj Co-authored-by: kangsun-ctrl <69279251+kangsun-ctrl@users.noreply.github.com>
@allenjzhang pls merge. this adds new 2020-12-01 gallery.json to sdk |
sdk/compute/Microsoft.Azure.Management.Compute/src/Microsoft.Azure.Management.Compute.csproj
Outdated
Show resolved
Hide resolved
sdk/compute/Microsoft.Azure.Management.Compute/src/Generated/GalleriesOperations.cs
Show resolved
Hide resolved
sdk/compute/Microsoft.Azure.Management.Compute/src/Generated/GalleriesOperationsExtensions.cs
Show resolved
Hide resolved
sdk/compute/Microsoft.Azure.Management.Compute/src/Generated/IGalleriesOperations.cs
Show resolved
Hide resolved
// these needs to be decided and created, especially subscription. | ||
// two gallery shared to the tenant, but only one gallery shared to the sub | ||
protected const string GalleryUniqueName = "97f78232-382b-46a7-8a72-964d692c4f3f-LONGLIVEGALLERYFOJNVV"; | ||
protected const string GalleryImageName = "jmaesscc"; |
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.
Are these resources that were created prior to running this test so the test could run?
If so, we HIGHLY advise to not do that. Have all the resource creation be automatic and in code, otherwise you will be responsible for their maintenance at all times.
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 long live resource that we also use for our bvt. So I think my team is responsible for their maintenance already. Also, I do not see any class initialization/cleanup decorator available. Without that, resource creation/cleanup is more troublesome.
protected const string GalleryImageName = "jmaesscc"; | ||
protected const string GalleryImageVersionName = "1.0.0"; | ||
|
||
private string galleryAccessLocation = "eastus2euap"; |
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.
Please use a non-Canary region for these tests.
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 as above
sdk/compute/Microsoft.Azure.Management.Compute/src/Customizations/GalleriesOperations.cs
Show resolved
Hide resolved
/// <param name='galleryName'> | ||
/// The name of the Shared Image Gallery. | ||
/// </param> | ||
public static async Task<Gallery> GetAsync(this IGalleriesOperations operations, string resourceGroupName, string galleryName) |
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.
The 'this' looks like incorrect syntax, remove it.
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 it is correct actually. VMSSOperationExtension has this too: https://github.com/kangsun-ctrl/azure-sdk-for-net/blob/master/sdk/compute/Microsoft.Azure.Management.Compute/src/Customizations/VirtualMachinesOperationsExtensions.cs
/// <param name='cancellationToken'> | ||
/// The cancellation token. | ||
/// </param> | ||
public static async Task<Gallery> GetAsync(this IGalleriesOperations operations, string resourceGroupName, string galleryName, CancellationToken cancellationToken = default(CancellationToken)) |
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.
The 'this' looks like incorrect syntax, remove it.
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 as above
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.
Just need to address the PR check failures before merging.
/azp |
Supported commands
See additional documentation. |
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
@allenjzhang please merge ! |
@markcowl , @allenjzhang , looks good to me! |
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
Draft
mode if it is:General Guidelines and Best Practices
Testing Guidelines
SDK Generation Guidelines
*.csproj
andAssemblyInfo.cs
files have been updated with the new version of the SDK. Please double check nuget.org current release version.Additional management plane SDK specific contribution checklist:
Note: Only applies to
Microsoft.Azure.Management.[RP]
orAzure.ResourceManager.[RP]
Management plane SDK Troubleshooting
new service
label and/or contact assigned reviewer.Verify Code Generation
step, please ensure:generate.ps1/cmd
to generate this PR instead of callingautorest
directly.Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,
Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.