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

Update HanaOnAzure Swagger to support new SKU: S96 #4773

Merged
merged 1 commit into from
Dec 5, 2018

Conversation

lagalbra
Copy link
Contributor

@lagalbra lagalbra commented Dec 4, 2018

Update spec and validate examples
- Make small correction to invalid HanaInstances_ListByResourceGroup example

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.

Update spec and validate examples
    - Make small correction to invalid HanaInstances_ListByResourceGroup example
@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 Dec 4, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#3277

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-js

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

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-java

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-go

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

@anuchandy anuchandy merged commit 5ba20f5 into Azure:master Dec 5, 2018
@lagalbra lagalbra deleted the lagalbra/new-sku-s96 branch December 6, 2018 18:11
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
Update spec and validate examples
    - Make small correction to invalid HanaInstances_ListByResourceGroup example
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
…urce provider (#4773)

* Added Access Profile resource for hpcworkbench

* fixed validation errors

* Updated access type in consortium and access profile properties

* updated access profil properties

* Fixed consortium and access profile properties

* updated consortium

* Removed List by Subscription and list by resource group for access profile

* Renamed file

* Fixed validation errors

* Added new resource chamber

* Resolved conflicts
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.

4 participants