Data source: azurerm_key_vault_certificate_data
- fix PEM private key block header for EC keys
#18419
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.
Currently
azurerm_key_vault_certificate_data
uses a general-----BEGIN PRIVATE KEY-----
header for EC private keys.This breaks tools like hashicorp/tls's
tls_locally_signed_cert
which expect PEM (RFC 1421) format forca_private_key_pem
:-----BEGIN EC PRIVATE KEY-----
.This was already fixed for RSA private keys in #12896. This PR does the same fix it for EC based keys too.
fixes #13965
Output from keyvault acceptance tests
There were a few failures here, but looks like it's just because I picked a bad location, and my service principal having limited access to Active Directory