| 1 |
Source: golang-github-azure-go-autorest |
| 2 |
Section: golang |
| 3 |
Priority: optional |
| 4 |
Standards-Version: 4.6.1 |
| 5 |
Maintainer: Debian Go Packaging Team <[email protected]> |
| 6 |
Uploaders: Martina Ferrari <[email protected]>, |
| 7 |
Tim Potter <[email protected]>, |
| 8 |
Build-Depends: debhelper-compat (= 13), |
| 9 |
dh-sequence-golang, |
| 10 |
golang-any, |
| 11 |
golang-github-dimchansky-utfbom-dev, |
| 12 |
golang-github-golang-jwt-jwt-dev, |
| 13 |
golang-github-mitchellh-go-homedir-dev, |
| 14 |
golang-github-stretchr-testify-dev, |
| 15 |
golang-golang-x-crypto-dev, |
| 16 |
Homepage: https://github.com/Azure/go-autorest |
| 17 |
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-azure-go-autorest |
| 18 |
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-azure-go-autorest.git |
| 19 |
XS-Go-Import-Path: github.com/Azure/go-autorest |
| 20 |
Rules-Requires-Root: no |
| 21 |
Testsuite: autopkgtest-pkg-go |
| 22 |
|
| 23 |
Package: golang-github-azure-go-autorest-dev |
| 24 |
Architecture: all |
| 25 |
Multi-Arch: foreign |
| 26 |
Depends: golang-github-dimchansky-utfbom-dev, |
| 27 |
golang-github-golang-jwt-jwt-dev, |
| 28 |
golang-github-mitchellh-go-homedir-dev, |
| 29 |
golang-golang-x-crypto-dev, |
| 30 |
${misc:Depends}, |
| 31 |
Description: HTTP request pipeline suitable for use across multiple go-routines |
| 32 |
Package autorest implements an HTTP request pipeline suitable for use across |
| 33 |
multiple go-routines and provides the shared routines relied on by AutoRest |
| 34 |
(see https://github.com/Azure/autorest/) generated Go code. |
| 35 |
. |
| 36 |
The package breaks sending and responding to HTTP requests into three phases: |
| 37 |
Preparing, Sending, and Responding. |
| 38 |
. |
| 39 |
Each phase relies on decorators to modify and / or manage processing. |
| 40 |
Decorators may first modify and then pass the data along, pass the data first |
| 41 |
and then modify the result, or wrap themselves around passing the data (such as |
| 42 |
a logger might do). Decorators run in the order provided. |
| 43 |
. |
| 44 |
Preparers and Responders may be shared and re-used (assuming the underlying |
| 45 |
decorators support sharing and re-use). Performant use is obtained by creating |
| 46 |
one or more Preparers and Responders shared among multiple go-routines, and a |
| 47 |
single Sender shared among multiple sending go-routines, all bound together by |
| 48 |
means of input / output channels. |
| 49 |
. |
| 50 |
Decorators hold their passed state within a closure (such as the path |
| 51 |
components in the example above). Be careful to share Preparers and Responders |
| 52 |
only in a context where such held state applies. For example, it may not make |
| 53 |
sense to share a Preparer that applies a query string from a fixed set of |
| 54 |
values. Similarly, sharing a Responder that reads the response body into a |
| 55 |
passed struct (e.g., ByUnmarshallingJson) is likely incorrect. |
| 56 |
. |
| 57 |
Lastly, the Swagger specification (https://swagger.io) that drives AutoRest |
| 58 |
(https://github.com/Azure/autorest/) precisely defines two date forms: date and |
| 59 |
date-time. The github.com/Azure/go-autorest/autorest/date package provides |
| 60 |
time.Time derivations to ensure correct parsing and formatting. |
| 61 |
. |
| 62 |
Errors raised by autorest objects and methods will conform to the |
| 63 |
autorest.Error interface. |