You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is part of the Azure SDK for JavaScript sample quality effort.
The new sample tool (dev-tool samples publish) has been made available to all package maintainers, and we would like to migrate all packages to the new system.
What do I need to do?
This issue is to track migrating all packages within the schemaregistry folder to the new layout:
schema-registry
schema-registry-avro
There are a few things to do to resolve this issue:
Attempt to follow the steps in the migration guide for each of the packages. Any problems can be reported to me, and I'll be available to assist in getting everything moved over.
Look at Samples Quality Effort Tracking Issue #14180, the main tracking issue for this work, and see if your package has any problems listed in the issue description. We would like to fix all of these issues that we are able to fix as we are migrating samples to the new system.
If for any reason you think that this issue should not apply to this service/package, please get in touch with me so that we can discuss the package's needs.
Thank you!
The text was updated successfully, but these errors were encountered:
Add new api version for Microsoft.AzureStackHCI (Azure#14480)
* Adds base for updating Microsoft.AzureStackHCI from version stable/2020-10-01 to version 2021-01-01-preview
* Updates readme
* Updates API version in new specs and examples
* Split spec file per resource type
* Use common type for operations response
* Add ArcSettings and Extensions resource types
* Fix readme.md
* Add examples
* Fix clusters spec
* Bring latest updates to clusters, extensions and arcSettings
* Flatten system data
This issue is part of the Azure SDK for JavaScript sample quality effort.
The new sample tool (
dev-tool samples publish
) has been made available to all package maintainers, and we would like to migrate all packages to the new system.What do I need to do?
This issue is to track migrating all packages within the schemaregistry folder to the new layout:
There are a few things to do to resolve this issue:
If for any reason you think that this issue should not apply to this service/package, please get in touch with me so that we can discuss the package's needs.
Thank you!
The text was updated successfully, but these errors were encountered: