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

Adding SQL managedDatabases swagger for API v2018-06-01-preview #7172

Merged
merged 11 commits into from
Sep 18, 2019

Conversation

misosic-msft
Copy link
Contributor

@misosic-msft misosic-msft commented Sep 10, 2019

Adding SQL managedDatabases swagger and examples for API version 2018-06-01-preview

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.

Adding managedDatabases swagger and examples for API version 2018-06-01-preview
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Sep 10, 2019

In Testing, Please Ignore

[Logs] (Generated from 65fd128, Iteration 10)

Warning .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
  • No packages generated.
Succeeded Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Failed Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]
In-Progress Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
  • In-Progress preview/sql/mgmt/2015-05-01-preview [Logs]
  • In-Progress preview/sql/mgmt/2017-03-01-preview [Logs]
  • In-Progress preview/sql/mgmt/2017-10-01-preview [Logs]
  • In-Progress preview/sql/mgmt/2018-06-01-preview [Logs]
  • In-Progress sql/mgmt/2014-04-01 [Logs]
Failed JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
Succeeded Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]

@AutorestCI
Copy link

AutorestCI commented Sep 10, 2019

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#7330

@AutorestCI
Copy link

AutorestCI commented Sep 10, 2019

Automation for azure-sdk-for-go

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@misosic-msft
Copy link
Contributor Author

I've run autorest validation and got the following:
image

1st, 3rd and 4th are already present in version 2017-03-01-preview of managedDatabases swagger.
For the 2nd warning, restoreDetails is always a single resource. Can we override this warning and skip implementing List?

@michaeljqzq
Copy link
Contributor

WARNING is not required to be fixed. But I see there's some error in semantic validation: 'internal error: Failed to load a reference file specification/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/examples/CompleteManagedRestore.json. (Error: ENOENT: no such file or directory
Please confirm

@misosic-msft
Copy link
Contributor Author

WARNING is not required to be fixed. But I see there's some error in semantic validation: 'internal error: Failed to load a reference file specification/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/examples/CompleteManagedRestore.json. (Error: ENOENT: no such file or directory
Please confirm

Added the missing file and resolved the validation test failures.

@michaeljqzq michaeljqzq added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Sep 16, 2019
@michaeljqzq
Copy link
Contributor

I added the DoNotMerge tag since the title. Do you have a timeline for the PR to merge?

@misosic-msft
Copy link
Contributor Author

misosic-msft commented Sep 16, 2019

I added the DoNotMerge tag since the title. Do you have a timeline for the PR to merge?

Changes for this API are already being rolled out to Production so it can be merged right away if everything looks good. I've removed [DO NOT MERGE] from the title.

@misosic-msft misosic-msft changed the title [DO NOT MERGE] Adding SQL managedDatabases swagger for API v2018-06-01-preview Adding SQL managedDatabases swagger for API v2018-06-01-preview Sep 16, 2019
@misosic-msft
Copy link
Contributor Author

@michaeljqzq @jaredmoo Can this PR be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DoNotMerge <valid label in PR review process> use to hold merge after approval
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants