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

duplicate operationIds in Microsoft.Sql 2022-02-01-preview #20067

Open
cataggar opened this issue Aug 2, 2022 · 2 comments
Open

duplicate operationIds in Microsoft.Sql 2022-02-01-preview #20067

cataggar opened this issue Aug 2, 2022 · 2 comments
Labels
Service Attention Workflow: This issue is responsible by Azure service team. SQL

Comments

@cataggar
Copy link
Member

cataggar commented Aug 2, 2022 •
edited
Loading

An operation named DatabaseSqlVulnerabilityAssessmentBaselines_CreateOrUpdate is defined twice in the same spec. The operationIds need to be unique. From PR #19820.

specification\sql\resource-manager\Microsoft.Sql\preview\2022-02-01-preview\

image

cc @ericshape, @raych1
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 2, 2022
@cataggar cataggar mentioned this issue Aug 2, 2022
Merged
@JackTn JackTn added SQL Service Attention Workflow: This issue is responsible by Azure service team. labels Aug 18, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 18, 2022
@ghost
Copy link

ghost commented Aug 18, 2022

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.

Issue Details

An operation named DatabaseSqlVulnerabilityAssessmentBaselines_CreateOrUpdate is defined twice in the same spec. The operationIds need to be unique. From PR #19820.

specification\sql\resource-manager\Microsoft.Sql\preview\2022-02-01-preview\

image

cc @ericshape, @raych1

Author: cataggar
Assignees: -
Labels:

SQL, Service Attention, needs-triage
Milestone: -

@ericshape
Copy link
Contributor

we have a fix in #19953
but no idea why this one still cannot be merged.

@ericshape ericshape mentioned this issue Aug 22, 2022
Merged
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Service Attention Workflow: This issue is responsible by Azure service team. SQL
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ericshape @JackTn @cataggar