This repository is for active development of the Azure SDK for Go. For consumers of the SDK you can follow the links below to visit the documentation you are interested in

• Overview of Azure SDK for Go
• SDK Reference
• Code Samples for Azure Go SDK
• Azure REST API Docs
• General Azure Docs
• Share your feedback to our Azure SDK

To get started with a module, see the README.md file located in the module's project folder. You can find these module folders grouped by service in the /sdk directory.

NOTE: Go 1.18 or later is required. You could download and install the latest version of Go from here. It will replace the existing Go on your machine. If you want to install multiple Go versions on the same machine, you could refer this doc.

NOTE: The root azure-sdk-for-go Go module which contains subpaths of /services/**/mgmt/** (also known as track 1) is deprecated and no longer recieving support. See the migration guide to learn how to migrate to the current version.

Each service can have both 'client' and 'management' modules. 'Client' modules are used to consume the service, whereas 'management' modules are used to configure and manage the service.

Our client modules follow the Azure Go SDK guidelines. These modules allow you to use, consume, and interact with existing resources, for example, uploading a blob. They also share a number of core functionalities including retries, logging, transport protocols, authentication protocols, etc. that can be found in the azcore module.

You can find the most up-to-date list of new modules on our latest page.

NOTE: If you need to ensure your code is ready for production use one of the stable, non-beta modules.

Similar to our client modules, the management modules follow the Azure Go SDK guidelines. All management modules are available at sdk/resourcemanager. These modules provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity module, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more.

To get started, please follow the quickstart guide here. To see the benefits of migrating and how to migrate to the new modules, please visit the migration guide.

You can find the most up to date list of all of the new packages on our page

NOTE: If you need to ensure your code is ready for production use one of the stable, non-beta modules. Also, if you are experiencing authentication issues with the management modules after upgrading certain packages, it's possible that you upgraded to the new versions of SDK without changing the authentication code. Please refer to the migration guide for proper instructions.

• Quickstart tutorial for new releases. Documentation is also available at each readme file of the individual module (Example: Readme for Compute Module)

More code samples for using the management modules for Go SDK can be found in the following locations

• Go SDK Code Samples Repo
• Example files under each package. For example, examples for Network packages can be found here

Note that the latest modules from Microsoft are grouped by service in the /sdk directory. If you're using packages with prefix github.com/Azure/azure-sdk-for-go/services, github.com/Azure/azure-sdk-for-go/storage, github.com/Azure/azure-sdk-for-go/profiles, please consider migrating to the latest modules. You can find a mapping table from these historical releases to their equivalent here.

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

• File an issue via Github Issues
• Check previous questions or ask new ones on StackOverflow using azure and go tags.

• Chat with us in the #Azure SDK channel on the Gophers Slack. Sign up here first if necessary.

See CONTRIBUTING.md.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.