Updated the version of cloudposse/ssm-tls-self-signed-cert/aws" to 1.3.0 #80
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
…signed-cert/aws" to 1.3.0
|
This is happening to me today after upgrading
The latest module version that allows TLS provider v4 is |
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.
what
Updated the version of referenced module
cloudposse/ssm-tls-self-signed-cert/awsto 1.3.0why
The current versions referenced in this module use an older version that does not allow the more recently released tls provider to be used. This causes conflicts if trying to add this module to an environment were a 4.0.x version of the tls provider was already used, which would happen easily since that is the current version.
references
closes #79