Skip to content

Comments

Instance Metadata Service: Initial Commit#4493

Merged
amarzavery merged 15 commits intoAzure:masterfrom
rifrankl:rifrankl-imds-Microsoft.InstanceMetadataService-2018-10-01
Dec 19, 2018
Merged

Instance Metadata Service: Initial Commit#4493
amarzavery merged 15 commits intoAzure:masterfrom
rifrankl:rifrankl-imds-Microsoft.InstanceMetadataService-2018-10-01

Conversation

@rifrankl
Copy link
Contributor

Initial commit of Instance Metadata Service

The Azure Instance Metadata Service provides information about running virtual machine instances that can be used to manage and configure them.

-Added Swagger for 2018-10-01
-Added examples for 2018-10-01

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.

Initial commit of Instance Metadata Service

-Added Swagger for 2018-10-01
-Added examples for 2018-10-01
@openapi-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@AutorestCI
Copy link

AutorestCI commented Nov 16, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Nov 16, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Nov 16, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Nov 16, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Nov 16, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Nov 16, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@salameer
Copy link
Member

reassinging since @sarangan12 is oof

@rifrankl please fix the validation errors. you can check them through the OpenAPI Hub here

@ravbhatnagar ravbhatnagar added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Nov 20, 2018
@amarzavery
Copy link
Contributor

Please add language specific reademe..md files for go, nodejs, ruby, typescript, python.

Take a look at this example.

@amarzavery
Copy link
Contributor

amarzavery commented Nov 20, 2018

@rifrankl -

  • What do you mean by initial commit? Is the service already deployed? If it is not yet deployed then is there any ETA? We cannot merge the PR to master if the service is not deployed to Prod.
  • If it will take multiple revisions for this swagger to become stable and that would also involve service api changes, then we would recommend creating a feature branch. PRs can be merged into this feature branch and once you are stable/comfortable then a final PR can be made to master from the feature branch. Please go over here to create a feature branch.
    • If required, the feature branch can be white listed, so that they can be assigned reviewers from our side.
  • Was this approved by ARM team? If not then you need to get this approved from ARM first and make sure you fix all the ARM linter errors.

@KrisBash KrisBash added ARMChangesRequested and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Nov 26, 2018
-Removed erroneous format tags
-Added security section
-Moved to imds/data-plane from imds/resource-provider
-Removed individual error codes from operations
-Created separate Identity error property
-Updated descriptions and added them where necessary
-Created parameters section and moved api-version and Metadata to it
-Renamed operationIds
-Removed previous API versions from enum
@rifrankl
Copy link
Contributor Author

The remaining errors are errors for which we would like an exception. See email thread from 11/20

@amarzavery amarzavery merged commit 7119de0 into Azure:master Dec 19, 2018
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
* Instance Metadata Service: Initial Commit

Initial commit of Instance Metadata Service

-Added Swagger for 2018-10-01
-Added examples for 2018-10-01

* Instance Metadata Service: Updates

-Removed erroneous format tags
-Added security section

* Instance Metadata Service: Updates

-Moved to imds/data-plane from imds/resource-provider

* Instance Metadata Service: Added language .md files

* Instance Metadata Service: Updated ErrorResponse

-Removed individual error codes from operations

* Instance Metadata Service: Updates to Swagger

-Created separate Identity error property
-Updated descriptions and added them where necessary
-Created parameters section and moved api-version and Metadata to it
-Renamed operationIds

* Added x-ms-parameter-location to Metadata parameter

* -Minor property name changes
-Removed previous API versions from enum

* -Fixed a typo

* -Added missing descriptions

* -Added more missing descriptions

* -Changed openapi type to data-plane

* -Added DefinitionsPropertiesNamesCamelCase suppression to readme

* -Forgot one camelcase suppression

* -Removed a newline
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants