-
Notifications
You must be signed in to change notification settings - Fork 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
mgmt, add generated samples for premium mgmt SDKs #25431
mgmt, add generated samples for premium mgmt SDKs #25431
Conversation
|
||
// move generated samples to azure-resourcemanager | ||
generatedSamplesSource = path.join(mappings[project].dir, '/src/samples/java/', packagePath, 'generated'); | ||
generatedSamplesTarget = path.join('azure-resourcemanager/src/samples/java/', packagePath); |
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.
do we need /generated folder?
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.
Want to have the /generated folder, so it is clear that these are pure generated, and might not have guarantee on its quality.
* use spec main branch * regen compute * pom * codegen to generate samples and move to azure-resourcemanager * samples for storage * samples for network * samples for compute * samples for ACR * samples for eventhubs * samples for cosmos * samples for AKS * clean sample target folder
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
fix #25320
Add generated samples for premium mgmt SDKs.
Main change is on the nodejs script 880527f
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines