chore(deps): update terraform tls to v4 #45
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.
This PR contains the following updates:
~>3.1
->~> 4.0
Release Notes
hashicorp/terraform-provider-tls (tls)
v4.0.6
Compare Source
NOTES:
v4.0.5
Compare Source
NOTES:
v4.0.4
Compare Source
BUG FIXES:
terraform refresh
updates state when cert is ready for renewal (#278).terraform refresh
updates state when cert is ready for renewal (#278).v4.0.3
Compare Source
BUG FIXES:
Config Read Error
with Terraform version 1.3.0 and laterConfig Read Error
with Terraform version 1.3.0 and laterv4.0.2
Compare Source
BUG FIXES:
v4.0.1
Compare Source
BUG FIXES:
empty list of object
error withcertificates
attribute (#244).v4.0.0
Compare Source
NOTES:
Provider has been re-written using the new
terraform-plugin-framework
(#215).resource/tls_cert_request:
private_key_pem
attribute is now stored in the state as-is; first apply may result in an update-in-place (#87, #215).resource/tls_self_signed_cert:
private_key_pem
attribute is now stored in the state as-is; first apply may result in an update-in-place (#87, #215).resource/tls_locally_signed_cert:
cert_request_pem
,ca_private_key_pem
andca_cert_pem
attributes are now stored in the state as-is; first apply may result in an update-in-place (#87, #215).resource/tls_private_key:
private_key_pem_pkcs8
,private_key_openssh
andpublic_key_fingerprint_sha256
attributes are now retro-fitted, depending on version being updated; first apply may result in an update-in-place (#210, #225)).ENHANCEMENTS:
private_key_pem_pkcs8
(PKCS#8) (#210, #225)).BREAKING CHANGES:
resource/tls_cert_request: Attribute
key_algorithm
is now read-only, as it's inferred fromprivate_key_pem
(#174, #215).resource/tls_self_signed_cert: Attribute
private_key_pem
is stored (and returned) as-is (in accordance with guidelines) (#87, #215).resource/tls_self_signed_cert: Attribute
key_algorithm
is now read-only, as it's inferred fromprivate_key_pem
(#174, #215).resource/tls_self_signed_cert: Setting an unsupported value in
allowed_uses
attribute, will now return an error instead of just a warning (#185, #215).resource/tls_self_signed_cert: Attribute
private_key_pem
is stored (and returned) as-is (in accordance with guidelines) (#87, #215).resource/tls_locally_signed_cert: Attribute
ca_key_algorithm
is now read-only, as it's inferred fromca_private_key_pem
(#174, #215).resource/tls_locally_signed_cert: Setting an unsupported value in
allowed_uses
attribute, will now return an error instead of just a warning (#185, #215).resource/tls_locally_signed_cert: Attributes
cert_request_pem
,ca_private_key_pem
,ca_cert_pem
are stored (and returned) as-is (in accordance with guidelines) (#87, #215).provider: Default value for
proxy.from_env
is nowtrue
, and relies uponhttpproxy.FromEnvironment
(#224).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.