New Base Layer to replace go-autorest #122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
release-once-merged
manicminer
force-pushed
the
base-layer
branch
from
f3a765e to
6c3b9ea
Compare
github-actions
bot
removed
the
release-once-merged
manicminer
force-pushed
the
base-layer
branch
11 times, most recently
from
c7e3fd9 to
36aff20
Compare
tombuildsstuff
force-pushed
the
base-layer
branch
from
5c8033a to
da80bcc
Compare
|
Is there a schedule for this PR release? so we can use the new base layer for Automation services, I am trying to fix the broken resources that exist in azurerm. both of them are because of the autorest bug and the service team's unwilling to fix the swagger 😫 |
tombuildsstuff
force-pushed
the
base-layer
branch
from
da80bcc to
f6a54c2
Compare
manicminer
force-pushed
the
base-layer
branch
from
f6a54c2 to
3671e14
Compare
tombuildsstuff
force-pushed
the
base-layer
branch
from
3671e14 to
c686b5f
Compare
tombuildsstuff
force-pushed
the
base-layer
branch
from
5f67394 to
6f2b2d6
Compare
- use native crypto types, avoid double decoding raw cert/key data - rename CLientFederatedAuth to OIDCAuth - test for OIDC authentication - change some return types to pointers - refactoring to support future signing algorithms
… in the UserAgent
…ed for SharedKeyAuthentication This also involves changing the HTTP Request pipeline such that we build the token from the HTTP Request at Execution time rather than when the HTTP Request is first created.
This enables us to dynamically poll on either a LRO or a provisioningState field, if one is found
tombuildsstuff
force-pushed
the
base-layer
branch
from
5fd4b54 to
f814228
Compare
|
The Base Layer needs to account for an error being returned via a 200 OK too, see: hashicorp/terraform-provider-azurerm#19849 (comment) |
… request when a response has no Content-Type header
tombuildsstuff
approved these changes
Jan 25, 2023
manicminer
commented
Jan 26, 2023
Co-authored-by: Tom Harvey <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: hashicorp/pandora#1309