-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Base layer migration #20320
Base layer migration #20320
Conversation
204e6a5
to
2052d71
Compare
2052d71
to
4397afd
Compare
Reworked so that much fewer service package client changes are needed for existing autorest-based SDK consumers, and stock service clients should continue to work as-is. No existing services will be migrated as part of this PR, in order to minimise the scope/size. |
ea8cc1d
to
ddbe0ba
Compare
ddbe0ba
to
5e3bfa8
Compare
5e3bfa8
to
548cec8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments inline but this otherwise LGTM 👍
|
||
EnableAuthenticatingUsingClientCertificate: true, | ||
EnableAuthenticatingUsingClientSecret: true, | ||
EnableAuthenticatingUsingAzureCLI: enableAzureCli, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a reason why we're introducing a feature-flag for this rather than defaulting it on?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AzureAD has had this property for awhile, the intention is to provide a means of disabling CLI auth in noninteractive environments, which helps with error messages (which a lot of users report as a red herring) since instead of getting a failure mentioning Azure CLI, you'd get an error stating that no authentication methods could be configured.
website/docs/guides/service_principal_client_certificate.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/guides/service_principal_client_certificate.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/guides/service_principal_client_certificate.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/guides/service_principal_client_certificate.html.markdown
Outdated
Show resolved
Hide resolved
548cec8
to
5c4439d
Compare
5c4439d
to
cef7384
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - nice work @manicminer 👍
This functionality has been released in v3.44.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Note: draft branch contains changes from hashicorp/go-azure-sdk#283, hashicorp/go-azure-sdk#284, hashicorp/go-azure-sdk#285 and https://github.com/hashicorp/go-azure-helpers/pull/149/files, in addition to go-azure-sdk built from main.Still a bunch of fixes to make,not compiling yet.Related: hashicorp/go-azure-helpers#149 although not required for this change
Note: update when hashicorp/go-azure-sdk#291 is merged
Working Changelog
ENHANCEMENTS:
github.com/manicminer/hamilton
[Base layer migration #20320]v0.20230206.1135314
ofgit.luolix.top/hashicorp/go-azure-sdk
[Base layer migration #20320]client_certificate
provider property [Base layer migration #20320]use_cli
provider property [Base layer migration #20320]TODO