storage scenario #19979

liurunliang · 2022-07-27T11:51:45Z

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?
- new service onboarding
- new API version
- update existing version for new feature
- update existing version to fix swagger quality issue in s360
- Other, please clarify
When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
- SDK of .NET (need service team to ensure code readiness)
- SDK of Python
- SDK of Java
- SDK of Js
- SDK of Go
- PowerShell
- CLI
- Terraform
- No refresh required for updates in this PR

Contribution checklist:

I commit to follow the Breaking Change Policy of "no breaking changes"
I have reviewed the documentation for the workflow.
Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs

Adding new properties

All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
- Adding a new service
- Adding new API(s)
- Adding a new API version
  -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

Removing API(s) in a stable version
Removing properties in a stable version
Removing API version(s) in a stable version
Updating API in a stable or public preview version with Breaking Change Validation errors
Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

openapi-workflow-bot · 2022-07-27T11:51:48Z

Hi, @liurunliang Thanks for your PR. I am workflow bot for review process. Here are some small tips.

Please ensure to do self-check against checklists in first PR comment.

PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.

For specs comparison cross API versions, Use API Specs Comparison Report Generator

If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com

openapi-pipeline-app · 2022-07-27T11:51:48Z

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️LintDiff succeeded [Detail] [Expand]

Validation passes for LintDiff.

compared tags (via openapi-validator v1.13.0)	new version	base version
default	default(8e8aff4)	default(apiscenario)

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️SDK Track2 Validation succeeded [Detail] [Expand]

Validation passes for SDKTrack2Validation

️️✔️PrettierCheck succeeded [Detail] [Expand]

Validation passes for PrettierCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️CadlValidation succeeded [Detail] [Expand]

Validation passes for CadlValidation.

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2022-07-27T11:51:49Z

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

️⚠️SDK Breaking Change Tracking warning [Detail]

Breaking Changes Tracking

⚠️azure-sdk-for-go - armstorage - 2.0.0

+	Field `Parameters` of struct `BlobContainersClientCreateOrUpdateImmutabilityPolicyOptions` has been removed
+	Field `Parameters` of struct `TableClientCreateOptions` has been removed
+	Field `Parameters` of struct `TableClientUpdateOptions` has been removed
+	Function `*BlobContainersClient.CreateOrUpdateImmutabilityPolicy` parameter(s) have been changed from `(context.Context, string, string, string, *BlobContainersClientCreateOrUpdateImmutabilityPolicyOptions)` to `(context.Context, string, string, string, ImmutabilityPolicy, *BlobContainersClientCreateOrUpdateImmutabilityPolicyOptions)`
+	Function `*TableClient.Create` parameter(s) have been changed from `(context.Context, string, string, string, *TableClientCreateOptions)` to `(context.Context, string, string, string, Table, *TableClientCreateOptions)`
+	Function `*TableClient.Update` parameter(s) have been changed from `(context.Context, string, string, string, *TableClientUpdateOptions)` to `(context.Context, string, string, string, Table, *TableClientUpdateOptions)`

️✔️azure-sdk-for-python-track2 - track2_azure-mgmt-storage - 20.0.0

️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 3354745. SDK Automation 14.0.0

command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
warn	File azure-sdk-for-net_tmp/initOutput.json not found to read
command	pwsh ./eng/scripts/Automation-Sdk-Generate.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json

️✔️Azure.ResourceManager.Storage [View full logs] [Release SDK Changes]
- Azure.ResourceManager.Storage.1.0.0-alpha.20220727.1.nupkg
- Azure.ResourceManager.Storage.1.0.0-alpha.20220727.1.symbols.nupkg
```
info	[Changelog]
```

️⚠️ azure-sdk-for-python-track2 warning [Detail]

⚠️Warning [Logs]Release - Generate from 3354745. SDK Automation 14.0.0

command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
cmderr	[automation_generate.sh] WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

️✔️track2_azure-mgmt-storage [View full logs] [Release SDK Changes]
- azure-mgmt-storage-20.0.0.zip
- azure_mgmt_storage-20.0.0-py3-none-any.whl
```
info	[Changelog]
```

️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 3354745. SDK Automation 14.0.0

command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json

️✔️azure-resourcemanager-storage-generated [View full logs] [Release SDK Changes]

️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 3354745. SDK Automation 14.0.0

command	sh ./eng/scripts/automation_init.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
command	generator automation-v2 ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json

️✔️armstorage [View full logs] [Release SDK Changes] Breaking Change Detected

info	[Changelog] ### Breaking Changes
info	[Changelog]
info	[Changelog] - Function `*BlobContainersClient.CreateOrUpdateImmutabilityPolicy` parameter(s) have been changed from `(context.Context, string, string, string, *BlobContainersClientCreateOrUpdateImmutabilityPolicyOptions)` to `(context.Context, string, string, string, ImmutabilityPolicy, *BlobContainersClientCreateOrUpdateImmutabilityPolicyOptions)`
info	[Changelog] - Function `*TableClient.Create` parameter(s) have been changed from `(context.Context, string, string, string, *TableClientCreateOptions)` to `(context.Context, string, string, string, Table, *TableClientCreateOptions)`
info	[Changelog] - Function `*TableClient.Update` parameter(s) have been changed from `(context.Context, string, string, string, *TableClientUpdateOptions)` to `(context.Context, string, string, string, Table, *TableClientUpdateOptions)`
info	[Changelog] - Field `Parameters` of struct `TableClientCreateOptions` has been removed
info	[Changelog] - Field `Parameters` of struct `TableClientUpdateOptions` has been removed
info	[Changelog] - Field `Parameters` of struct `BlobContainersClientCreateOrUpdateImmutabilityPolicyOptions` has been removed
info	[Changelog]
info	[Changelog] Total 6 breaking change(s), 0 additive change(s).

️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 3354745. SDK Automation 14.0.0

command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
cmderr	[automation_generate.sh] npm [ERROR] Cannot generate changelog because the codes of local and npm may be the same.

️✔️@azure/arm-storage [View full logs] [Release SDK Changes]

azure-arm-storage-17.2.2.tgz

info	[Changelog]
error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.

️⚠️ azure-resource-manager-schemas warning [Detail]

⚠️Warning [Logs]Release - Generate from 3354745. Schema Automation 14.0.0

command	.sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
cmderr	[initScript.sh]  old lockfile
cmderr	[initScript.sh] npm WARN old lockfile The package-lock.json file was created with an old version of npm,
cmderr	[initScript.sh] npm WARN old lockfile so supplemental metadata must be fetched from the registry.
cmderr	[initScript.sh] npm WARN old lockfile
cmderr	[initScript.sh] npm WARN old lockfile This is a one-time fix-up, please be patient...
cmderr	[initScript.sh] npm WARN old lockfile
warn	File azure-resource-manager-schemas_tmp/initOutput.json not found to read
command	.sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
warn	No file changes detected after generation

️✔️storage [View full logs]

️️✔️ azure-powershell succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 3354745. SDK Automation 14.0.0

command	sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json
command	pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json

️✔️Az.Storage [View full logs] [Release SDK Changes]
- Az.Storage.0.1.0.nupkg

_{Posted by Swagger Pipeline | How to fix these errors?}

storage scenario

8e8aff4

liurunliang requested a review from JasonYang-MSFT as a code owner July 27, 2022 11:51

openapi-assignment-bot bot assigned jianyexi Jul 27, 2022

leni-msft approved these changes Jul 27, 2022

View reviewed changes

leni-msft merged commit 3354745 into Azure:apiscenario Jul 27, 2022

azure-sdk mentioned this pull request Jul 27, 2022

[ReleasePR armstorage] change the name of a new enumeration in storage's latest api-version Azure/azure-sdk-for-go#17935

Closed

openapi-pipeline-app bot added the CI-BreakingChange-Go label Jul 27, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

storage scenario #19979

storage scenario #19979

liurunliang commented Jul 27, 2022

openapi-workflow-bot bot commented Jul 27, 2022

openapi-pipeline-app bot commented Jul 27, 2022 •

edited

Loading

openapi-pipeline-app bot commented Jul 27, 2022 •

edited

Loading

Breaking Changes Tracking

storage scenario #19979

storage scenario #19979

Conversation

liurunliang commented Jul 27, 2022

Changelog

Contribution checklist:

ARM API Review Checklist

Breaking Change Review Checklist

openapi-workflow-bot bot commented Jul 27, 2022

openapi-pipeline-app bot commented Jul 27, 2022 • edited Loading

Swagger Validation Report

openapi-pipeline-app bot commented Jul 27, 2022 • edited Loading

Swagger Generation Artifacts

Breaking Changes Tracking

openapi-pipeline-app bot commented Jul 27, 2022 •

edited

Loading

openapi-pipeline-app bot commented Jul 27, 2022 •

edited

Loading