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.

Sign up for GitHub

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

Jump to bottom

IMDS: Adding Swagger spec for 2019-04-30 version. #6572

Merged
merged 3 commits into from
Jul 23, 2019
Merged

IMDS: Adding Swagger spec for 2019-04-30 version. #6572

merged 3 commits into from
Jul 23, 2019

Conversation

tushar-bhargava-ms
Copy link
Contributor

@tushar-bhargava-ms tushar-bhargava-ms commented Jul 9, 2019 •
edited
Loading

Contribution checklist:

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jul 9, 2019 •
edited
Loading

SDK Automation [Logs] (Generated from ffc69bc, Iteration 9)

Warning Python: Azure/azure-sdk-for-python [Logs] [Diff]
  • No packages generated.

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2019 •
edited
Loading

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2019 •
edited
Loading

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2019 •
edited
Loading

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@azuresdkci azuresdkci requested a review from yaohaizh July 9, 2019 21:06
@yaohaizh yaohaizh added the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Jul 11, 2019
@yaohaizh
Copy link
Contributor

There is already a version of 2019-06-01, does this version necessary? Thanks.

@yaohaizh yaohaizh removed the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Jul 22, 2019
@tushar-bhargava-ms
Copy link
Contributor Author

@yaohaizh , yes, this version is necessary even though it's seemingly identical to the 2019-06-01 version. IMDS has several different providers, and they all share the same versions: The 2019-04-30 version is required by the attested provider for a new subscription ID field.

@yaohaizh yaohaizh merged commit 5795c13 into Azure:master Jul 23, 2019
leni-msft pushed a commit to leni-msft/azure-rest-api-specs that referenced this pull request May 13, 2022
@krishnasriSomepalli
Adding Microsoft.Confluent 2022-03-01 to fix S360 + IcM issue (Azure#…
0aa2acb 
…6572)

* Adds base for updating Microsoft.Confluent from version stable/2021-12-01 to version 2022-03-01

* Updates readme

* Updates API version in new specs and examples

* Removing maxLength + fixing linting issues (Azure#6574)

* Removing maxLength + fixing linting issue

* Updating confluent.json for Swagger Linting fix

https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=9DA38F21-FFDA-4909-A86F-189CC09155D7

* Update confluent.json

* LintDiff, changing api-version type

* Update confluent.json (Azure#6674)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yaohaizh yaohaizh yaohaizh approved these changes

Assignees

@yaohaizh yaohaizh

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@tushar-bhargava-ms @azuresdkci @AutorestCI @yaohaizh