[Stream Analytics] Fix validStreamingUnits Property

[roslynlu]

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:

1. 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
2. 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.
3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
4. If updating an existing version, please select the specific langauge 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 apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

  • Adding a new service
  • Adding new API(s)
  • Adding a new API version
    -[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

• 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]

Hi, @roslynlu 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. vsswagger@microsoft.com

[openapi-workflow-bot]

[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

[openapi-pipeline-app]

Swagger Validation Report

️❌BreakingChange: 1 Errors, 1 Warnings failed [Detail]

• Compared Swaggers (Based on Oad v0.9.0)
  • current:stable/2020-03-01/transformations.json compared with base:stable/2020-03-01/transformations.json

Rule	Message
❌ 1023 - TypeFormatChanged	The new version has a different format than the previous one. New: Microsoft.StreamAnalytics/stable/2020-03-01/transformations.json#L266:9 Old: Microsoft.StreamAnalytics/stable/2020-03-01/transformations.json#L266:9
⚠️ 1026 - TypeChanged	The new version has a different type 'array' than the previous one 'integer'. New: Microsoft.StreamAnalytics/stable/2020-03-01/transformations.json#L266:9 Old: Microsoft.StreamAnalytics/stable/2020-03-01/transformations.json#L266:9

️⚠️LintDiff: 0 Warnings warning [Detail]

• Linted configuring files (Based on source branch, openapi-validator v1.10.1 , classic-openapi-validator v1.1.10 )
  • streamanalytics/resource-manager/readme.md tag:package-pure-2020-03
• Linted configuring files (Based on target branch, openapi-validator v1.10.1 , classic-openapi-validator v1.1.10 )
  • streamanalytics/resource-manager/readme.md tag:package-pure-2020-03

The following errors/warnings exist before current PR submission:

Rule	Message
❌ R4015 - NestedResourcesMustHaveListOperation	The nested resource 'Transformation' does not have list operation, please add it. Location: Microsoft.StreamAnalytics/stable/2020-03-01/transformations.json#L241
❌ R4037 - MissingTypeObject	The schema 'properties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.StreamAnalytics/stable/2020-03-01/subscriptions.json#L104
⚠️ R2001 - AvoidNestedProperties	Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.StreamAnalytics/stable/2020-03-01/functions.json#L469
⚠️ R2001 - AvoidNestedProperties	Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.StreamAnalytics/stable/2020-03-01/inputs.json#L433
⚠️ R2010 - LongRunningOperationsOptionsValidator	A LRO Post operation with return schema must have 'x-ms-long-running-operation-options' extension enabled. Location: Microsoft.StreamAnalytics/stable/2020-03-01/inputs.json#L364
⚠️ R2010 - LongRunningOperationsOptionsValidator	A LRO Post operation with return schema must have 'x-ms-long-running-operation-options' extension enabled. Location: Microsoft.StreamAnalytics/stable/2020-03-01/outputs.json#L409
⚠️ R2010 - LongRunningOperationsOptionsValidator	A LRO Post operation with return schema must have 'x-ms-long-running-operation-options' extension enabled. Location: Microsoft.StreamAnalytics/stable/2020-03-01/functions.json#L343
⚠️ R2029 - PageableOperation	Based on the response model schema, operation 'Subscriptions_ListQuotas' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.StreamAnalytics/stable/2020-03-01/subscriptions.json#L37
⚠️ R3010 - TrackedResourceListByImmediateParent	The child tracked resource, 'transformations' with immediate parent 'StreamingJob', must have a list by immediate parent operation. Location: Microsoft.StreamAnalytics/stable/2020-03-01/transformations.json#L241
⚠️ R3018 - EnumInsteadOfBoolean	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDataAction Location: Microsoft.StreamAnalytics/stable/2020-03-01/streamingjobs.json#L605
⚠️ R3018 - EnumInsteadOfBoolean	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isConfigurationParameter Location: Microsoft.StreamAnalytics/stable/2020-03-01/functions.json#L540
⚠️ R4014 - AllResourcesMustHaveGetOperation	The resource 'SubscriptionQuota' does not have get operation, please add it. Location: Microsoft.StreamAnalytics/stable/2020-03-01/subscriptions.json#L95

️⚠️Avocado: 1 Warnings warning [Detail]

Rule	Message
⚠️ MULTIPLE_API_VERSION	The default tag contains multiple API versions swaggers. readme: specification/streamanalytics/resource-manager/readme.md tag: specification/streamanalytics/resource-manager/readme.md#tag-package-2020-03-preview

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

Validation passes for ModelValidation.

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

Validation passes for SemanticValidation.

️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

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

Validation passes for SDKTrack2Validation

• The following tags are being changed in this PR
• streamanalytics/resource-manager/readme.md#package-pure-2020-03

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

Validation passes for PrettierCheck.

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

Validation passes for SpellCheck.

️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

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

[openapi-pipeline-app]

Swagger Generation Artifacts

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

 Please click here to preview with your @microsoft account. 

️❌[Staging] SDK Breaking Change Tracking failed [Detail]

Breaking Changes Tracking

️✔️azure-sdk-for-python-track2 - track2_azure-mgmt-streamanalytics - 1.0.0rc1
❌azure-sdk-for-go - streamanalytics/mgmt/2016-03-01/streamanalytics - Approved - v57.4.0

+	Field `Location` of struct `Resource` has been removed
+	Field `Tags` of struct `Resource` has been removed

️✔️azure-sdk-for-go - preview/streamanalytics/mgmt/2020-03-01-preview/streamanalytics - Approved - v57.4.0

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

• ️✔️Succeeded [Logs]Release - Generate from 0e16aa6. SDK Automation 14.0.0

  warn	Skip initScript due to not configured
  command	sudo apt-get install -y dotnet-sdk-5.0
  command	autorest --version=V2 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.csharp@2.3.82 --csharp-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/streamanalytics/resource-manager/readme.md
  cmderr	[Autorest] realpath(): Permission denied
  cmderr	[Autorest] realpath(): Permission denied
  cmderr	[Autorest] realpath(): Permission denied
  cmderr	[Autorest] realpath(): Permission denied
  cmderr	[Autorest] realpath(): Permission denied
  cmderr	[Autorest] realpath(): Permission denied

• ️✔️Microsoft.Azure.Management.StreamAnalytics [View full logs]  [Release SDK Changes]
  • Microsoft.Azure.Management.StreamAnalytics.3.0.0-preview.nupkg
  • Microsoft.Azure.Management.StreamAnalytics.3.0.0-preview.symbols.nupkg

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

• ⚠️Warning [Logs]Release - Generate from 0e16aa6. 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

• ️✔️track2_azure-mgmt-streamanalytics [View full logs]  [Release SDK Changes]
  • azure-mgmt-streamanalytics-1.0.0b1.zip
  • azure_mgmt_streamanalytics-1.0.0b1-py2.py3-none-any.whl

  info	[Changelog] **Features**
  info	[Changelog]
  info	[Changelog]   - Added operation SubscriptionsOperations.compile_query
  info	[Changelog]   - Added operation SubscriptionsOperations.begin_test_query
  info	[Changelog]   - Added operation SubscriptionsOperations.begin_test_input
  info	[Changelog]   - Added operation SubscriptionsOperations.begin_test_output
  info	[Changelog]   - Added operation SubscriptionsOperations.begin_sample_input

️❌ azure-sdk-for-go failed [Detail]

• ❌Failed [Logs]Release - Generate from 0e16aa6. SDK Automation 14.0.0

  command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
  command	generator automation ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
  cmderr	[generator automation] [ERROR] open /home/vsts/work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/tools/pkgchk/exceptions.txt: no such file or directory
  error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go]: generator automation
  warn	Skip package processing as generation is failed

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

• ️✔️Succeeded [Logs]Release - Generate from 0e16aa6. SDK Automation 14.0.0

  warn	Skip initScript due to not configured
  command	autorest --version=V2 --typescript --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.typescript@4.7.0 --typescript-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-js/azure-sdk-for-js ../../azure-rest-api-specs/specification/streamanalytics/resource-manager/readme.md

• ️✔️@azure/arm-streamanalytics [View full logs]  [Release SDK Changes]
  • azure-arm-streamanalytics-2.1.1.tgz

  cmderr	[npmPack] loaded rollup.config.js with warnings
  cmderr	[npmPack] (!) Unused external imports
  cmderr	[npmPack] default imported from external module 'rollup' but never used
  cmderr	[npmPack] ./esm/streamAnalyticsManagementClient.js → ./dist/arm-streamanalytics.js...
  cmderr	[npmPack] created ./dist/arm-streamanalytics.js in 525ms

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

• ⚠️Warning [Logs]Release - Generate from 0e16aa6. 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] WARN 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

• ️✔️streamanalytics [View full logs]  [Release Schema Changes]

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

[openapi-workflow-bot]

Hi @roslynlu, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
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.
If you want to know the production traffic statistic, please see ARM Traffic statistic.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

[roslynlu]

hi @ArcturusZhang, got breaking change sign off, can this PR be merged?