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

fix schema property naming #6901

Merged
merged 2 commits into from
Aug 14, 2019
Merged

fix schema property naming #6901

merged 2 commits into from
Aug 14, 2019

Conversation

alargeasteroid
Copy link
Contributor

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.

@AutorestCI
Copy link

AutorestCI commented Aug 8, 2019

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Aug 8, 2019

Automation for azure-sdk-for-python

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@@ -828,18 +828,6 @@
}
}
},
"KnowledgebaseEnvironment": {
Copy link
Member

Choose a reason for hiding this comment

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

Is this removal considered as a breaking change? Breaking changes should not happen in a stable version

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My understanding is that this is only used once for this file's redundant schema reference. I would assume that removing this has no breaking impact on the schema. Are you aware of a reason this would be a breaking change?

Copy link
Member

Choose a reason for hiding this comment

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

So you are saying that removal of this schema will not cause a breaking change. If so, I am ok with this, and will approve this as soon as azure api board responds

Copy link
Member

Choose a reason for hiding this comment

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

Is there a change to the REST API that motivated this change?

Copy link
Member

Choose a reason for hiding this comment

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

Per offline conversation, this is not a change to the public REST API. Thus, no need for the Azure API review board to review.

Copy link
Member

@ArcturusZhang ArcturusZhang Aug 14, 2019

Choose a reason for hiding this comment

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

Hi @alargeasteroid after a check on SDK, this removal will cause a breaking change on go SDK (we have a tool for that). But in my opinion, this situation happens day to day, we always get unexpected breaking changes in SDK and in semver we will hold this kind of breaking change to next major version release

@ArcturusZhang ArcturusZhang added the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Aug 9, 2019
@johanste johanste removed the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Aug 14, 2019
@ArcturusZhang
Copy link
Member

Approved and merged

@ArcturusZhang ArcturusZhang merged commit f23355b into Azure:master Aug 14, 2019
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Aug 14, 2019

In Testing, Please Ignore

[Logs] (Generated from faa8f71, Iteration 1)

leni-msft pushed a commit to leni-msft/azure-rest-api-specs that referenced this pull request May 13, 2022
* new easm api

* updating based on semantics

* updating based on semantics

* updating easm

* updating easm

* updating versions and rp name

* updating description

* updates based on comments

* fixing validation errors

Co-authored-by: Sonia Burney <sonia.burney@riskiq.net>
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.

5 participants