You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Adding new API(s)
Adding a new API version
Adding a new service
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 there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Removing API(s) in stable version
Removing properties in stable version
Removing API version(s) in stable version
Updating API in stable version with Breaking Change Validation errors
️✔️ Generate from c72a0a9 with merge commit cd08fff2ea7dbbaf2cdfb0b57218fb667790bbe6. Schema Automation 13.0.17.20200918.2
[confluent][after_scripts|node] configure: WARNING: secure clearing/zeroing of memory is not supported by the selected crypto backend
[confluent][after_scripts|node] configure: WARNING: secure clearing/zeroing of memory is not supported by the selected crypto backend
[confluent][after_scripts|node] configure: WARNING: secure clearing/zeroing of memory is not supported by the selected crypto backend
❌ Generate from c72a0a9 with merge commit cd08fff2ea7dbbaf2cdfb0b57218fb667790bbe6. Azure CLI Automation 13.0.17.20200918.2
[AutoRest] WARNING (PreCheck/AllOfWhenYouMeantRef): Schema 'OrganizationResourceProperties-offerDetail' is using an 'allOf' instead of a $ref. This creates a wasteful anonymous type when generating code.
[AutoRest] WARNING (PreCheck/AllOfWhenYouMeantRef): Schema 'OrganizationResourceProperties-userDetail' is using an 'allOf' instead of a $ref. This creates a wasteful anonymous type when generating code.
[AutoRest] WARNING (PreCheck/AllOfWhenYouMeantRef): Schema 'OrganizationResource-properties' is using an 'allOf' instead of a $ref. This creates a wasteful anonymous type when generating code.
[AutoRest] WARNING (PreCheck/SchemaMissingType): The schema 'OrganizationResourceProperties-offerDetail' with an undefined type and 'allOf'/'anyOf'/'oneOf' is a bit ambigious. This has been auto-corrected to 'type:object'
[AutoRest] WARNING (PreCheck/SchemaMissingType): The schema 'OrganizationResourceProperties-userDetail' with an undefined type and 'allOf'/'anyOf'/'oneOf' is a bit ambigious. This has been auto-corrected to 'type:object'
[AutoRest] WARNING (PreCheck/SchemaMissingType): The schema 'OrganizationResource-properties' with an undefined type and 'allOf'/'anyOf'/'oneOf' is a bit ambigious. This has been auto-corrected to 'type:object'
[AutoRest] WARNING (PreCheck/SchemaMissingType): The schema 'AgreementTerms' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'
[AutoRest] WARNING (PreCheck/SchemaMissingType): The schema 'AgreementProperties' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'
[AutoRest] WARNING (PreCheck/SchemaMissingType): The schema 'Resource' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'
[AutoRest] WARNING (PreCheck/CheckDuplicateSchemas): Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail.
[AutoRest] WARNING (PreNamer/DeduplicateName): Deduplicating schema name: 'organization_resource_properties' -> 'organization_resource_propertiesAutoGenerated'
[AutoRest] WARNING (): cli.auto-parameter-hidden is not true, skip visibility cleaner
[AutoRest] ERROR: probably missing readme.az.md possible settings are:
[AutoRest] az:
[AutoRest] extensions: managed-network
[AutoRest] namespace: azure.mgmt.managednetwork
[AutoRest] package-name: azure-mgmt-managednetwork
[AutoRest] python-sdk-output-folder: "$(output-folder)/src/managed-network/azext_managed_network/vendored_sdks/managed-network"
[AutoRest]
[AutoRest] FATAL: Error: name should not be null
[AutoRest] (node:114) UnhandledPromiseRejectionWarning: Error: Plugin azgenerator reported failure.
[AutoRest] at /home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/plugins/external.js:26:19
[AutoRest] at async ScheduleNode (/home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/pipeline.js:294:33)
[AutoRest] (Use `node --trace-warnings ...` to show where the warning was created)
[AutoRest] (node:114) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40)
[AutoRest] (node:114) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[AutoRest] (node:114) UnhandledPromiseRejectionWarning: Error: Plugin azgenerator reported failure.
[AutoRest] at /home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/plugins/external.js:26:19
[AutoRest] at async ScheduleNode (/home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/pipeline.js:294:33)
[AutoRest] (node:114) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 41)
[AutoRest] Error: Plugin azgenerator reported failure.
Failed to run autorest.
Error: /z/node_modules/.bin/autorest --az --use=@autorest/az@latest --version=3.0.6271 --clear-output-folder=true --azure-cli-extension-folder=/z/work/azure-cli-extensions /z/work/azure-rest-api-specs/specification/confluent/resource-manager/readme.md ERROR: probably missing readme.az.md possible settings are:
az:
extensions: managed-network
namespace: azure.mgmt.managednetwork
package-name: azure-mgmt-managednetwork
python-sdk-output-folder: "$(output-folder)/src/managed-network/azext_managed_network/vendored_sdks/managed-network"
FATAL: Error: name should not be null
(node:114) UnhandledPromiseRejectionWarning: Error: Plugin azgenerator reported failure.
at /home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/plugins/external.js:26:19
at async ScheduleNode (/home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/pipeline.js:294:33)
(Use node --trace-warnings ... to show where the warning was created)
(node:114) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40)
(node:114) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:114) UnhandledPromiseRejectionWarning: Error: Plugin azgenerator reported failure.
at /home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/plugins/external.js:26:19
at async ScheduleNode (/home/sdk/.autorest/@[email protected]/node_modules/@autorest/core/dist/lib/pipeline/pipeline.js:294:33)
(node:114) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 41)
Error: Plugin azgenerator reported failure.
, {}
Failed to find any diff after autorest so no changed packages was found.
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
[build_conf] INFO:packaging_tools:Building template azure-mgmt-confluent
[build_conf] INFO:packaging_tools.conf:Build default conf for azure-mgmt-confluent
[build_conf] INFO:packaging_tools:Template done azure-mgmt-confluent
[build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
[build_package] warnings.warn(msg)
[build_package] /z/venv/lib/python3.6/site-packages/setuptools/dist.py:406: UserWarning: The version specified ('2020-03-01-preview') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
[build_package] "details." % self.metadata.version
[build_package] warning: no files found matching '*.py' under directory 'tests'
[build_package] warning: no files found matching '*.yaml' under directory 'tests'
[build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
[build_package] warnings.warn(msg)
[build_package] /z/venv/lib/python3.6/site-packages/setuptools/dist.py:406: UserWarning: The version specified ('2020-03-01-preview') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
[build_package] "details." % self.metadata.version
[build_package] warning: no files found matching '*.py' under directory 'tests'
[build_package] warning: no files found matching '*.yaml' under directory 'tests'
[breaking_change_setup] Ignoring mock: markers 'python_version <= "2.7"' don't match your environment
Not exact 2 reports found:
Not generating changelog.
[ChangeLog] WARNING: Failed to generate ChangeLog.
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
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 there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.