Skip to content
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

[Microsoft.Advisor] Add applicableScenarios property to metadata entity properties. (API is not live yet) #6067

Merged
merged 16 commits into from
May 24, 2019

Conversation

mudit794
Copy link
Contributor

@mudit794 mudit794 commented May 22, 2019

Latest improvements:

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

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@mudit794 mudit794 changed the title Add isAlertable property to metadata entity properties. (API is not live yet) [Microsoft.Advisor] Add isAlertable property to metadata entity properties. (API is not live yet) May 22, 2019
@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented May 22, 2019

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#5133

@AutorestCI
Copy link

AutorestCI commented May 22, 2019

Automation for azure-sdk-for-js

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-js#3200

@AutorestCI
Copy link

AutorestCI commented May 22, 2019

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#4874

adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request May 22, 2019
REST Spec PR 'Azure/azure-rest-api-specs#6067'
REST Spec PR Author 'mudit794'
REST Spec PR Last commit
@adxsdknet
Copy link

adxsdknet commented May 22, 2019

Automation for azure-sdk-for-net

A PR has been created for you:
Azure/azure-sdk-for-net#6390
.NET SDK Commits:
adxsdknet/azure-sdk-for-net@2fc54b3
adxsdknet/azure-sdk-for-net@ced452e

@AutorestCI
Copy link

AutorestCI commented May 22, 2019

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@nschonni
Copy link
Contributor

To make the spelling happy, you'd need to add "Alertable" to the words array in https://github.com/Azure/azure-rest-api-specs/blob/master/cSpell.json#L5

@AutorestCI
Copy link

AutorestCI commented May 22, 2019

Automation for azure-sdk-for-java

Encountered a Subprocess error: (azure-sdk-for-java)

Command: ['/usr/local/bin/autorest', '/tmp/tmp0vj1krb5/rest/specification/advisor/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpvoy9umc2']
Finished with return code 7
and output:

AutoRest code generation utility [version: 2.0.4283; node: v8.12.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Failure:
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core
    at main (/opt/node_modules/autorest/dist/app.js:232:19)
    at <anonymous>

/root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core/dist/app.js:33
    autorest_core_1.Shutdown();
    ^
ReferenceError: autorest_core_1 is not defined
    at process.on (/root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core/dist/app.js:33:5)
    at emitOne (events.js:121:20)
    at process.emit (events.js:211:7)
    at process.emit (/node_modules/source-map-support/source-map-support.js:439:21)
fs.js:612
  return binding.close(fd);
                 ^

Error: EBADF: bad file descriptor, close
    at Object.fs.closeSync (fs.js:612:18)
    at StaticVolumeFile.shutdown (/opt/node_modules/autorest/dist/static-loader.js:352:10)
    at StaticFilesystem.shutdown (/opt/node_modules/autorest/dist/static-loader.js:406:17)
    at process.exit.n [as exit] (/opt/node_modules/autorest/dist/static-loader.js:169:11)
    at printErrorAndExit (/node_modules/source-map-support/source-map-support.js:423:11)
    at process.emit (/node_modules/source-map-support/source-map-support.js:435:16)
    at process._fatalException (bootstrap_node.js:391:26)

@mudit794
Copy link
Contributor Author

To make the spelling happy, you'd need to add "Alertable" to the words array in https://github.com/Azure/azure-rest-api-specs/blob/master/cSpell.json#L5

Added "Alertable" in spell.json.

node SDK failure is known thing. It is due to some infra issue.

@ryansbenson ryansbenson added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label May 23, 2019
@ryansbenson ryansbenson added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 23, 2019
adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request May 24, 2019
REST Spec PR 'Azure/azure-rest-api-specs#6067'
REST Spec PR Author 'mudit794'
REST Spec PR Last commit
@mudit794 mudit794 changed the title [Microsoft.Advisor] Add isAlertable property to metadata entity properties. (API is not live yet) [Microsoft.Advisor] Add applicableScenarios property to metadata entity properties. (API is not live yet) May 24, 2019
@ryansbenson ryansbenson added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels May 24, 2019
Copy link
Contributor

@ryansbenson ryansbenson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signed off from ARMs side

@sergey-shandar sergey-shandar merged commit 657587d into Azure:master May 24, 2019
@mudit794 mudit794 deleted the advisor/AddAlertFieldToMetadata branch May 24, 2019 21:43
dsgouda pushed a commit to Azure/azure-sdk-for-net that referenced this pull request May 28, 2019
* .NET SDK Resource Provider:'Advisor'
REST Spec PR 'Azure/azure-rest-api-specs#6067'
REST Spec PR Author 'mudit794'
REST Spec PR Last commit

* .NET SDK Resource Provider:'Advisor'
REST Spec PR 'Azure/azure-rest-api-specs#6067'
REST Spec PR Author 'mudit794'
REST Spec PR Last commit
mentat9 pushed a commit to mentat9/azure-sdk-for-net that referenced this pull request Jun 10, 2019
* .NET SDK Resource Provider:'Advisor'
REST Spec PR 'Azure/azure-rest-api-specs#6067'
REST Spec PR Author 'mudit794'
REST Spec PR Last commit

* .NET SDK Resource Provider:'Advisor'
REST Spec PR 'Azure/azure-rest-api-specs#6067'
REST Spec PR Author 'mudit794'
REST Spec PR Last commit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants