-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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 ARMViolations for Microsoft.Solutions #3914
Conversation
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goA 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: |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
@marstr Can you please take a look at this validation error? It is not related with my change. It seems that in the file, we have path "/{applianceId}" and "/{applianceDefinitionId}", and validation thinks they are the same path. |
Seems like this must be a long-standing issue, as running a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, making properties optional after they're required can break what we code-gen. However, because this is in the preview
folder, we do not block on breaking changes.
@sergey-shandar, is this a known issue? |
Signing off from ARM side. |
@marstr Thanks, please merge this PR. |
Automation for azure-sdk-for-jsNothing to generate for azure-sdk-for-js |
Fix ARMViolations for Microsoft.Solutions