Fix links to be https instead of http (#7003)
This commit is contained in:
Wes Haggard
GitHub
Родитель
792bf8d363
Коммит
c4ca95862d
10
README.md
10
README.md
|
|
@ -72,11 +72,11 @@ contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additio
|
|||
[azure-sdk-for-js Repository]: https://github.com/Azure/azure-sdk-for-js
|
||||
[azure-sdk-for-python Repository]: https://github.com/Azure/azure-sdk-for-python
|
||||
|
||||
[Official Azure Documentation]: http://aka.ms/azure-sdk-docs
|
||||
[.NET Documentation]: http://aka.ms/net-docs
|
||||
[Go Documentation]: http://aka.ms/go-docs
|
||||
[Java Documentation]: http://aka.ms/java-docs
|
||||
[JavaScript Documentation]: http://aka.ms/js-docs
|
||||
[Official Azure Documentation]: https://aka.ms/azure-sdk-docs
|
||||
[.NET Documentation]: https://aka.ms/net-docs
|
||||
[Go Documentation]: https://aka.ms/go-docs
|
||||
[Java Documentation]: https://aka.ms/java-docs
|
||||
[JavaScript Documentation]: https://aka.ms/js-docs
|
||||
[Python Documentation]: https://aka.ms/python-docs
|
||||
[C Documentation]: https://aka.ms/c-docs
|
||||
[C++ Documentation]: https://aka.ms/cpp-docs
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
{% endif %}
|
||||
|
||||
<div class="{{ include.type | default: "list" }}__item">
|
||||
<article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork">
|
||||
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
|
||||
{% if include.type == "grid" and teaser %}
|
||||
<div class="archive__item-teaser">
|
||||
<img src=
|
||||
|
|
|
|||
|
|
@ -1046,7 +1046,7 @@ Filenames should be concise, but convey what role the file plays within the libr
|
|||
|
||||
### Documentation Style
|
||||
|
||||
{% include requirement/MUST id="clang-docs-doxygen" %} include docstrings compatible with the [doxygen](http://www.doxygen.nl/index.html) tool for generating reference documentation.
|
||||
{% include requirement/MUST id="clang-docs-doxygen" %} include docstrings compatible with the [doxygen](https://www.doxygen.nl/index.html) tool for generating reference documentation.
|
||||
|
||||
For example, a (very) simple docstring might look like:
|
||||
{% highlight c %}
|
||||
|
|
|
|||
|
|
@ -571,7 +571,7 @@ TEST_FUNCTION(foo_tcp_manager_create_createAndReturnInstanceSucceed)
|
|||
}
|
||||
{% endhighlight %}
|
||||
|
||||
{% include requirement/MUSTNOT id="clang-testing-valgrind" %} have any memory leaks. Run samples and unit tests with [valgrind](http://www.valgrind.org/downloads/current.html). Unit tests and e2e tests are valgrind verified at the gate.
|
||||
{% include requirement/MUSTNOT id="clang-testing-valgrind" %} have any memory leaks. Run samples and unit tests with [valgrind](https://www.valgrind.org/downloads/current.html). Unit tests and e2e tests are valgrind verified at the gate.
|
||||
|
||||
{% include requirement/MUST id="clang-testing-unittests" %} unit test your API with [ccputest](https://cpputest.github.io/), a unit testing and mocking framework for C and C++.
|
||||
|
||||
|
|
@ -664,7 +664,7 @@ generate_export_header(appconf
|
|||
EXPORT_FILE_NAME az/appconf_export.h)
|
||||
{% endhighlight %}
|
||||
|
||||
{% include requirement/MUST id="clang-tooling-clang-format" %} use [clang-format](http://clang.llvm.org/docs/ClangFormat.html) for formatting, with the following command-line options:
|
||||
{% include requirement/MUST id="clang-tooling-clang-format" %} use [clang-format](https://clang.llvm.org/docs/ClangFormat.html) for formatting, with the following command-line options:
|
||||
|
||||
{% highlight bash %}
|
||||
clang-format -style=file -i <file> ...
|
||||
|
|
@ -711,7 +711,7 @@ endif()
|
|||
|
||||
## Formatting
|
||||
|
||||
{% include requirement/MUST id="clang-format-clang" %} use [clang-format](http://clang.llvm.org/docs/ClangFormat.html) for formatting your code. Use the common `clang-format` options from Engineering Systems.
|
||||
{% include requirement/MUST id="clang-format-clang" %} use [clang-format](https://clang.llvm.org/docs/ClangFormat.html) for formatting your code. Use the common `clang-format` options from Engineering Systems.
|
||||
|
||||
In general, clang-format will format your code correctly and ensure consistency. However, these are few additional rules to keep in mind.
|
||||
|
||||
|
|
@ -859,7 +859,7 @@ do so using user-overridable functions.
|
|||
|
||||
## Secure functions
|
||||
|
||||
{% include requirement/SHOULDNOT id="clang-no-ms-secure-functions" %} use [Microsoft security enhanced versions of CRT functions](https://docs.microsoft.com/cpp/c-runtime-library/security-enhanced-versions-of-crt-functions) to implement APIs that need to be portable across many platforms. Such code is not portable and is not C99 compatible. Adding that code to your API will complicate the implementation with little to no gain from the security side. See [arguments against]( http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm).
|
||||
{% include requirement/SHOULDNOT id="clang-no-ms-secure-functions" %} use [Microsoft security enhanced versions of CRT functions](https://docs.microsoft.com/cpp/c-runtime-library/security-enhanced-versions-of-crt-functions) to implement APIs that need to be portable across many platforms. Such code is not portable and is not C99 compatible. Adding that code to your API will complicate the implementation with little to no gain from the security side. See [arguments against]( https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm).
|
||||
|
||||
> TODO: Verify with the security team, and what are the alternatives?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
| Library | Version | Usage |
|
||||
|------------|---------|-----------------------------------------------------|
|
||||
| libxml2 | 2.7.6 | XML parser - http://www.xmlsoft.org/ |
|
||||
| libxml2 | 2.7.6 | XML parser - https://www.xmlsoft.org/ |
|
||||
| gtest | 1.10.0 | Google Test - https://github.com/google/googletest/ |
|
||||
|
||||
> Note: None of the libraries in this list currently throw C++ exceptions; policy for propagation
|
||||
|
|
|
|||
|
|
@ -502,7 +502,7 @@ struct Foo {
|
|||
|
||||
#### Const and Reference members
|
||||
|
||||
{% include requirement/MUSTNOT id="cpp-design-logical-no-const-or-reference-members" %} declare types with const or reference members. Const and reference members artificially make your types non-Regular as they aren't assignable, and have surprising interactions with C++ Core language rules. For example, many accesses to const or reference members would need to involve use of `std::launder` to avoid undefined behavior, but `std::launder` was added in C++17, a later version than the SDKs currently target. See C++ Core Working Group [CWG1116 "Aliasing of union members"](http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1116), [CWG1776 "Replacement of class objects containing reference members"](http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1776), and [P0137R1 "Replacement of class objects containing reference members"](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0137r1.html) for additional details.
|
||||
{% include requirement/MUSTNOT id="cpp-design-logical-no-const-or-reference-members" %} declare types with const or reference members. Const and reference members artificially make your types non-Regular as they aren't assignable, and have surprising interactions with C++ Core language rules. For example, many accesses to const or reference members would need to involve use of `std::launder` to avoid undefined behavior, but `std::launder` was added in C++17, a later version than the SDKs currently target. See C++ Core Working Group [CWG1116 "Aliasing of union members"](https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1116), [CWG1776 "Replacement of class objects containing reference members"](https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1776), and [P0137R1 "Replacement of class objects containing reference members"](https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0137r1.html) for additional details.
|
||||
|
||||
If you want a type to provide effectively const data except assignment, declare all your member functions const. Const member functions only get a const view of the class' data.
|
||||
|
||||
|
|
@ -544,7 +544,7 @@ The following integer rules are listed in rough priority order. Integer size sel
|
|||
|
||||
#### Secure functions
|
||||
|
||||
{% include requirement/SHOULDNOT id="cpp-design-logical-no-ms-secure-functions" %} use [Microsoft security enhanced versions of CRT functions](https://docs.microsoft.com/cpp/c-runtime-library/security-enhanced-versions-of-crt-functions) to implement APIs that need to be portable across many platforms. Such code is not portable and is not compatible with either the C or C++ Standards. See [arguments against]( http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm).
|
||||
{% include requirement/SHOULDNOT id="cpp-design-logical-no-ms-secure-functions" %} use [Microsoft security enhanced versions of CRT functions](https://docs.microsoft.com/cpp/c-runtime-library/security-enhanced-versions-of-crt-functions) to implement APIs that need to be portable across many platforms. Such code is not portable and is not compatible with either the C or C++ Standards. See [arguments against](https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm).
|
||||
|
||||
> TODO: Verify with the security team, and what are the alternatives?
|
||||
|
||||
|
|
@ -618,7 +618,7 @@ struct HashComputation {
|
|||
|
||||
#### Class Types (including `union`s and `struct`s)
|
||||
|
||||
Throughout this section, *class types* includes types with *class-key* `struct` or *class-key* `union`, consistent with the [C++ Standard](http://eel.is/c++draft/class#pre-4).
|
||||
Throughout this section, *class types* includes types with *class-key* `struct` or *class-key* `union`, consistent with the [C++ Standard](https://eel.is/c++draft/class#pre-4).
|
||||
|
||||
{% include requirement/MUST id="cpp-design-naming-classes" %} name class types with **PascalCase**.
|
||||
|
||||
|
|
@ -806,7 +806,7 @@ endif()
|
|||
|
||||
| Operating System | Version | Architectures | Compiler Version | Notes
|
||||
|---------------------------------|---------------|---------------|-----------------------------------------|------
|
||||
| Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7+ | x64 | gcc-4.8 | [Red Hat lifecycle](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://www.centos.org/centos-linux-eol/) <br> [Oracle Linux lifecycle](http://www.oracle.com/us/support/library/elsp-lifetime-069338.pdf)
|
||||
| Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7+ | x64 | gcc-4.8 | [Red Hat lifecycle](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://www.centos.org/centos-linux-eol/) <br> [Oracle Linux lifecycle](https://www.oracle.com/us/support/library/elsp-lifetime-069338.pdf)
|
||||
| Debian | 9+ | x64 | gcc-6.3 | [Debian lifecycle](https://wiki.debian.org/DebianReleases)
|
||||
| Ubuntu | 18.04, 16.04 | x64 | gcc-7.3 | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases)
|
||||
| Linux Mint | 18+ | x64 | gcc-7.3 | [Linux Mint lifecycle](https://www.linuxmint.com/download_all.php)
|
||||
|
|
|
|||
|
|
@ -722,7 +722,7 @@ dependency.
|
|||
|
||||
{% include requirement/MUST id="cpp-docs-document-everything" %} document every exposed (public or protected) type and member within your library's code.
|
||||
|
||||
{% include requirement/MUST id="cpp-docs-docstrings" %} use [doxygen](http://www.doxygen.nl/index.html) comments for reference documentation.
|
||||
{% include requirement/MUST id="cpp-docs-docstrings" %} use [doxygen](https://www.doxygen.nl/index.html) comments for reference documentation.
|
||||
|
||||
See the [documentation guidelines]({{ site.baseurl }}/general_documentation.html) for language-independent guidelines for how to provide good documentation.
|
||||
|
||||
|
|
@ -784,7 +784,7 @@ As you write your code, *doc it so you never hear about it again.* The less ques
|
|||
|
||||
**Docstrings**
|
||||
|
||||
{% include requirement/MUST id="cpp-docs-doxygen" %} include docstrings compatible with the [doxygen](http://www.doxygen.nl/index.html) tool for generating reference documentation.
|
||||
{% include requirement/MUST id="cpp-docs-doxygen" %} include docstrings compatible with the [doxygen](https://www.doxygen.nl/index.html) tool for generating reference documentation.
|
||||
|
||||
For example, a (very) simple docstring might look like:
|
||||
{% highlight cpp %}
|
||||
|
|
|
|||
|
|
@ -384,7 +384,7 @@ NOTE: If the client method allows the consumer to set arbitrary headers, then an
|
|||
|
||||
## Support for non-HTTP protocols
|
||||
|
||||
Most Azure services expose a RESTful API over HTTPS. However, a few services use other protocols, such as [AMQP](https://www.amqp.org/), [MQTT](http://mqtt.org/), or [WebRTC](https://webrtc.org/). In these cases, the operation of the protocol can be split into two phases:
|
||||
Most Azure services expose a RESTful API over HTTPS. However, a few services use other protocols, such as [AMQP](https://www.amqp.org/), [MQTT](https://mqtt.org/), or [WebRTC](https://webrtc.org/). In these cases, the operation of the protocol can be split into two phases:
|
||||
|
||||
* Per-connection (surrounding when the connection is initiated and terminated)
|
||||
* Per-operation (surrounding when an operation is sent through the open connection)
|
||||
|
|
|
|||
|
|
@ -5,8 +5,8 @@
|
|||
[BlockHound]: https://github.com/reactor/BlockHound
|
||||
[OpenTelemetry]: https://opentelemetry.io
|
||||
[Azure Monitor]: https://azure.microsoft.com/services/monitor/
|
||||
[SLF4J]: http://www.slf4j.org/
|
||||
[SLF4J user manual]: http://www.slf4j.org/manual.html
|
||||
[SLF4J]: https://www.slf4j.org/
|
||||
[SLF4J user manual]: https://www.slf4j.org/manual.html
|
||||
[azure/azure-sdk-for-java]: https://github.com/azure/azure-sdk-for-java
|
||||
[azure-sdk-for-java/parent/pom.xml]: https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/parents/azure-sdk-parent/pom.xml
|
||||
[1]: https://www.youtube.com/watch?v=PAAkCSZUG1c&t=9m28s
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ Depending on the situation and service, more than one SDK API review may be need
|
|||
| Core Concepts | Good to have | A glossary of nouns & verbs | [Example](https://github.com/Azure/azure-sdk-pr/blob/main/onboarding/Core_Concepts.pdf) |
|
||||
|
||||
|
||||
**APIView Note**: If you have a pull request for your changes, then you can use the automatically generated [APIView](http://apiview.dev/) reviews from the pull request to discuss the APIs with the Architecture Board. If you do not have a pull request and have a prototype of your APIs, you can generate the API listing in the [APIView](http://apiview.dev/) tool as mentioned [here](https://github.com/Azure/azure-sdk-tools/blob/main/src/dotnet/APIView/APIViewWeb/README.md#how-to-create-an-api-review-manually).
|
||||
**APIView Note**: If you have a pull request for your changes, then you can use the automatically generated [APIView](https://apiview.dev/) reviews from the pull request to discuss the APIs with the Architecture Board. If you do not have a pull request and have a prototype of your APIs, you can generate the API listing in the [APIView](https://apiview.dev/) tool as mentioned [here](https://github.com/Azure/azure-sdk-tools/blob/main/src/dotnet/APIView/APIViewWeb/README.md#how-to-create-an-api-review-manually).
|
||||
|
||||
## What happens during review
|
||||
|
||||
|
|
@ -110,7 +110,7 @@ It is expected that SDK API changes are released in beta for a period of time be
|
|||
|
||||
## Getting approval for small, targeted changes and bug fixes
|
||||
|
||||
For small or targeted changes and bug fixes which modify SDK APIs, the architect in each language can review and approve without a combined/central review. We highly recommend doing this review as early as possible. This should be done on GitHub by opening an issue with links to [APIView](http://apiview.dev/) diffs. Include all architects as reviewers. In some cases it makes sense for small changes to the SDK API to be batched for efficiency. If a language architect determines there is a need for a deeper discussion, then a meeting with that architect should be scheduled. If it’s a cross-language discussion, then a board meeting should be scheduled.
|
||||
For small or targeted changes and bug fixes which modify SDK APIs, the architect in each language can review and approve without a combined/central review. We highly recommend doing this review as early as possible. This should be done on GitHub by opening an issue with links to [APIView](https://apiview.dev/) diffs. Include all architects as reviewers. In some cases it makes sense for small changes to the SDK API to be batched for efficiency. If a language architect determines there is a need for a deeper discussion, then a meeting with that architect should be scheduled. If it’s a cross-language discussion, then a board meeting should be scheduled.
|
||||
|
||||
Remember that **all** changes to an SDK API must be approved by the language architect before a stable release.
|
||||
|
||||
|
|
|
|||
|
|
@ -768,7 +768,7 @@ Only applications are expected to pin exact dependencies. Libraries are not. A l
|
|||
|
||||
### Docstrings
|
||||
|
||||
{% include requirement/MUST id="python-docstrings-pydocs" %} follow the [documentation guidelines](http://aka.ms/pydocs) unless explicitly overridden in this document.
|
||||
{% include requirement/MUST id="python-docstrings-pydocs" %} follow the [documentation guidelines](https://aka.ms/pydocs) unless explicitly overridden in this document.
|
||||
|
||||
{% include requirement/MUST id="python-docstrings-all" %} provide docstrings for all public modules, types, constants and functions.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ As you write your code, *doc it so you never hear about it again.* The less ques
|
|||
|
||||
## Docstrings
|
||||
|
||||
{% include requirement/MUST id="python-docstrings-pydocs" %} follow the [documentation guidelines](http://aka.ms/pydocs) unless explicitly overridden in this document.
|
||||
{% include requirement/MUST id="python-docstrings-pydocs" %} follow the [documentation guidelines](https://aka.ms/pydocs) unless explicitly overridden in this document.
|
||||
|
||||
{% include requirement/MUST id="python-docstrings-all" %} provide docstrings for all public modules, types, and methods.
|
||||
|
||||
|
|
|
|||
|
|
@ -41,4 +41,4 @@ To register a new namespace, contact the [Architecture Board].
|
|||
[Form Recognizer]: https://azure.microsoft.com/services/cognitive-services/form-recognizer/
|
||||
[Key Vault]: https://azure.microsoft.com/services/key-vault/
|
||||
[Service Bus]: https://azure.microsoft.com/services/service-bus/
|
||||
[Text Analytics]: http://azure.microsoft.com/services/cognitive-services/text-analytics/
|
||||
[Text Analytics]: https://azure.microsoft.com/services/cognitive-services/text-analytics/
|
||||
|
|
|
|||
|
|
@ -661,7 +661,7 @@ TODO: Please add a section on extensible enums, if this is relevant to JS/TS.
|
|||
|
||||
## Support for non-HTTP protocols {#general-other-protocols}
|
||||
|
||||
Most Azure services expose a RESTful API over HTTPS. However, a few services use other protocols, such as [AMQP](https://www.amqp.org/), [MQTT](http://mqtt.org/), or [WebRTC](https://webrtc.org/). In these cases, the operation of the protocol can be split into two phases:
|
||||
Most Azure services expose a RESTful API over HTTPS. However, a few services use other protocols, such as [AMQP](https://www.amqp.org/), [MQTT](https://mqtt.org/), or [WebRTC](https://webrtc.org/). In these cases, the operation of the protocol can be split into two phases:
|
||||
|
||||
* Per-connection (surrounding when the connection is initiated and terminated)
|
||||
* Per-operation (surrounding when an operation is sent through the open connection)
|
||||
|
|
|
|||
|
|
@ -255,7 +255,7 @@ Let's take two examples:
|
|||
|
||||
## Testing TypeScript libraries
|
||||
|
||||
{% include requirement/SHOULD id="ts-use-mocha-karma" %} use [Mocha](https://mochajs.org/) and [Karma](http://karma-runner.github.io/4.0/index.html) as these tools support build pipelines and work in browsers and node.
|
||||
{% include requirement/SHOULD id="ts-use-mocha-karma" %} use [Mocha](https://mochajs.org/) and [Karma](https://karma-runner.github.io/4.0/index.html) as these tools support build pipelines and work in browsers and node.
|
||||
|
||||
## Versioning {#ts-versioning}
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ Detailed change logs are linked to in the Quick Links below. Here are some criti
|
|||
|
||||
* Designed based on the [Azure SDK Design Guidelines for Java][java-guidelines], resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, etc.
|
||||
* Modernized API making use of Java 8 features such as streams, new date / time, functional interfaces, etc, to offer an improved and more productive developer experience.
|
||||
* Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](http://projectreactor.io).
|
||||
* Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](https://projectreactor.io).
|
||||
|
||||
## Need help?
|
||||
* For reference documentation visit the [Azure SDK for Java documentation](https://azure.github.io/azure-sdk-for-java/).
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ Detailed change logs are linked to in the Quick Links below. Here are some criti
|
|||
|
||||
* Designed based on the [Azure SDK Design Guidelines for Java][java-guidelines], resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, etc.
|
||||
* Modernized API making use of Java 8 features such as streams, new date / time, functional interfaces, etc, to offer an improved and more productive developer experience.
|
||||
* Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](http://projectreactor.io).
|
||||
* Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](https://projectreactor.io).
|
||||
|
||||
### Azure Identity
|
||||
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ Detailed change logs are linked to in the Quick Links below. Here are some criti
|
|||
|
||||
- Designed based on the [Azure SDK Design Guidelines for Java]({{site.baseurl}}{% link docs/java/introduction.md %}), resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, etc.
|
||||
- Modernized API making use of Java 8 features such as streams, new date / time, functional interfaces, etc, to offer an improved and more productive developer experience.
|
||||
- Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](http://projectreactor.io).
|
||||
- Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](https://projectreactor.io).
|
||||
|
||||
### Azure Identity
|
||||
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ Detailed change logs are linked to in the Quick Links below. Here are some criti
|
|||
|
||||
- Designed based on the [Azure SDK Design Guidelines for Java]({{site.baseurl}}{% link docs/java/introduction.md %}), resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, etc.
|
||||
- Modernized API making use of Java 8 features such as streams, new date / time, functional interfaces, etc, to offer an improved and more productive developer experience.
|
||||
- Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](http://projectreactor.io).
|
||||
- Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](https://projectreactor.io).
|
||||
|
||||
### Event Hubs
|
||||
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@ Detailed change logs are linked to in the Quick Links below. Here are some criti
|
|||
|
||||
- Designed based on the [Azure SDK Design Guidelines for Java]({{site.baseurl}}{% link docs/java/introduction.md %}), resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, etc.
|
||||
- Modernized API making use of Java 8 features such as streams, new date / time, functional interfaces, etc, to offer an improved and more productive developer experience.
|
||||
- Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](http://projectreactor.io).
|
||||
- Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](https://projectreactor.io).
|
||||
|
||||
### App Configuration
|
||||
|
||||
|
|
|
|||
|
|
@ -234,7 +234,7 @@ Detailed changelogs are linked from the [Quick Links](#quick-links) below. Here
|
|||
### New Management Libraries
|
||||
A new set of management libraries that follow the [Azure SDK Design Guidelines for .NET](https://azure.github.io/azure-sdk/dotnet_introduction.html) and based on [Azure.Core libraries](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/core/Azure.Core) are now in Public Preview. These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. You can find the list of new packages [on this page](https://aka.ms/azsdk/releases).
|
||||
|
||||
To get started with these new libraries, please see the [quickstart guide here](http://aka.ms/azsdk/net/mgmt). These new libraries can be identifed by namespaces that start with `Azure.ResourceManager`, e.g. `Azure.ResourceManager.Network`
|
||||
To get started with these new libraries, please see the [quickstart guide here](https://aka.ms/azsdk/net/mgmt). These new libraries can be identifed by namespaces that start with `Azure.ResourceManager`, e.g. `Azure.ResourceManager.Network`
|
||||
|
||||
More details of recent management library release annoucements as well as future roadmap can be found at [this blog post](https://aka.ms/azsdk/blog/octmgmtga)
|
||||
|
||||
|
|
|
|||
|
|
@ -831,7 +831,7 @@ of the amqp connection.
|
|||
|
||||
### Management Libraries
|
||||
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Java](https://azure.github.io/azure-sdk/java/guidelines/). In addition, more management libraries are now in Public Preview to provide better Azure service coverage. These new libraries provide a higher-level, object-oriented API for managing Azure resources, that is optimized for ease of use, succinctness and consistency. You can find the list of new packages [on this page](https://azure.github.io/azure-sdk/releases/latest/java.html). Detailed documentation and code samples for these new libraries can be [found here](http://aka.ms/azsdk/java/mgmt)
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Java](https://azure.github.io/azure-sdk/java/guidelines/). In addition, more management libraries are now in Public Preview to provide better Azure service coverage. These new libraries provide a higher-level, object-oriented API for managing Azure resources, that is optimized for ease of use, succinctness and consistency. You can find the list of new packages [on this page](https://azure.github.io/azure-sdk/releases/latest/java.html). Detailed documentation and code samples for these new libraries can be [found here](https://aka.ms/azsdk/java/mgmt)
|
||||
|
||||
These new packages share the same groupId ``com.azures.resourcemanager`` and artifactId share the same prefix of ``azure-resourcemanager``
|
||||
|
||||
|
|
|
|||
|
|
@ -143,7 +143,7 @@ Detailed changelogs are linked from the [Quick Links](#quick-links) below. Here
|
|||
- Added support for getting the range diff between current file and a snapshot as well as getting the diff between two file snapshots.
|
||||
|
||||
### Management Libraries
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Python](https://azure.github.io/azure-sdk/python/guidelines/). These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. Documentation and code samples for these new libraries can be found [here](http://aka.ms/azsdk/python/mgmt)
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Python](https://azure.github.io/azure-sdk/python/guidelines/). These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. Documentation and code samples for these new libraries can be found [here](https://aka.ms/azsdk/python/mgmt)
|
||||
|
||||
More details of recent management library release annoucements as well as future roadmap can be found at [this blog post](https://aka.ms/azsdk/blog/octmgmtga)
|
||||
|
||||
|
|
|
|||
|
|
@ -304,7 +304,7 @@ If you have a bug or feature request for one of the libraries, please post an is
|
|||
|
||||
### Management Libraries
|
||||
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Java](https://azure.github.io/azure-sdk/java/guidelines/). In addition, more management libraries are now in Public Preview to provide better Azure service coverage. These new libraries provide a higher-level, object-oriented API for managing Azure resources, that is optimized for ease of use, succinctness and consistency. You can find the list of new packages [on this page](https://azure.github.io/azure-sdk/releases/latest/java.html). Detailed documentation and code samples for these new libraries can be [found here](http://aka.ms/azsdk/java/mgmt)
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Java](https://azure.github.io/azure-sdk/java/guidelines/). In addition, more management libraries are now in Public Preview to provide better Azure service coverage. These new libraries provide a higher-level, object-oriented API for managing Azure resources, that is optimized for ease of use, succinctness and consistency. You can find the list of new packages [on this page](https://azure.github.io/azure-sdk/releases/latest/java.html). Detailed documentation and code samples for these new libraries can be [found here](https://aka.ms/azsdk/java/mgmt)
|
||||
|
||||
These new packages share the same groupId ``com.azures.resourcemanager`` and artifactId share the same prefix of ``azure-resourcemanager``
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ If you have a bug or feature request for one of the libraries, please post an is
|
|||
## Release highlights
|
||||
|
||||
### Management Libraries
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Python](https://azure.github.io/azure-sdk/python/guidelines/). These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. Documentation and code samples for these new libraries can be found [here](http://aka.ms/azsdk/python/mgmt)
|
||||
We are excited to announce the GA releases of management libraries that follow the [Azure SDK Design Guidelines for Python](https://azure.github.io/azure-sdk/python/guidelines/). These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. Documentation and code samples for these new libraries can be found [here](https://aka.ms/azsdk/python/mgmt)
|
||||
|
||||
### Synapse
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче