f15c823e79
* Disable dependency on azure-core until azure-core releases to vcpkg. * Remove release artifact creation script and pipeline step * Copy items from root cmake generate outputs (no need to do individual project preparation) * Space * Add VcpkgPortName (package port names may change in the future to include non v1 version numbers like azure-template-cpp-v2) * Destination should be artifact name, not vcpkg port name * Disable PR steps * SHA512 1 -> SHA512 %SHA512% * New release procedure * Unblock publishing process * Increment azure-template version * Update branch strategy, uncomment final release of template * Increment version to test release * Fix remote branch checkout logic * Increment version * Exit successfully * Increment version * Increment Version * Version Increment * Add a difference in the output file to validate multiple runs against a target PR branch * Enable existing PR branches in create-pull-request.yml * Increment version * Fix archetype-cpp-release.yml syntax * Skip checkout instead * Increment version * Fix automated version incrementing * Increment version * Update CHANGELOG.md * Update CHANGELOG.md date * Revert CONTROL file * Remove Build-Depends * Increment version * Output commands * Check out branch in either branch scenario * Increment version * Fetch the .tar.gz file using convention, the REST API does not give the location of the .tar.gz * Increment Version * ToLower * Increment * Increment version * Version updater should not append a new line to the end of the file contents (existing new line at the end of the file will remain, if present) * Add azure-template2 to validate base case of shipping different packages instead of file replacement validation from previous runs * Remove extra backtick * Add template2 to root CMakeLists.txt * Review feedback: Support main scenario with packages coming from different location (no new file conflicts) * Remove file blocking link check step. This is ok because the whole azure-template2 folder will be removed after this verification is complete * Version increment * Make template2 install in different locations * Increment version * Remove azure-template2 that was used for validating publishing multiple packages * Remove template2 from ci.yml * Use "SHA512 1" syntax as proposed by vcpkg documentation and regex replacement * Review feedback * Increment version * Quotes * Review feedback and re-add New-ReleaseAsset.ps1 |
||
|---|---|---|
| .github | ||
| cmake-modules | ||
| doc | ||
| eng | ||
| samples | ||
| sdk | ||
| .clang-format | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CMakeSettings.json | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| README.md | ||
| SECURITY.md | ||
Azure SDK for C++
This repository is for active development of the Azure SDK for C++. For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs.
Getting started
To get started with a library, see the README.md file located in the library's project folder. You can find these library folders grouped by service in the /sdk directory.
For tutorials, samples, quick starts, and other documentation, go to Azure for C++ Developers.
Packages available
Each service might have a number of libraries available from each of the following categories:
Client: New Releases
New wave of packages that we are announcing as GA and several that are currently releasing in beta. These libraries follow the Azure SDK Design Guidelines for C++ and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. You can learn about these shared features at Azure::Core.
These new client libraries can be identified by the naming used for their folder, package, and namespace. Each will start with azure, followed by the service category, and then the name of the service. For example azure-storage-blobs.
For a complete list of available packages, please see the latest available packages page.
NOTE: If you need to ensure your code is ready for production we strongly recommend using one of the stable, non-beta libraries.
Client: Previous Versions
Last stable versions of packages that are production-ready. These libraries provide similar functionalities to the beta packages, as they allow you to use and consume existing resources and interact with them, for example: upload a storage blob. They might not implement the guidelines or have the same feature set. They do however offer wider coverage of services.
Need help
- For reference documentation visit the Azure SDK for C++ documentation.
- For tutorials, samples, quick starts and other documentation, visit Azure for C++ Developers.
- File an issue via Github Issues.
Navigating the repository
Master branch
The master branch has the most recent code with new features and bug fixes. It does not represent latest released beta or GA SDK.
Release branches (Release tagging)
For each package we release there will be a unique git tag created that contains the name and the version of the package to mark the commit of the code that produced the package. This tag will be used for servicing via hotfix branches as well as debugging the code for a particular beta or stable release version.
Format of the release tags are <package-name>_<package-version>. For more information please see our branching strategy.
Contributing
For details on contributing to this repository, see the contributing guide.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, view Microsoft's CLA.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Additional Helpful Links for Contributors
Many people all over the world have helped make this project better. You'll want to check out:
- What are some good first issues for new contributors to the repo?
- How to build and test your change
- How you can make a change happen!
- Frequently Asked Questions (FAQ) and Conceptual Topics in the detailed Azure SDK for C++ wiki.
Reporting security issues and security bugs
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. 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.
License
Azure SDK for C++ is licensed under the MIT license.
