Fix connecting encrypted ebs volumes to aws_instances #1718
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
ravenac95
changed the title
|
This looks fantastic. Thanks! |
mitchellh
added a commit
that referenced
this pull request
Apr 29, 2015
provider/aws: Fix connecting encrypted ebs volumes to aws_instances
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I found out, after working with
terraformtoday that when you applied theencrypted = trueoption for aebs_block_devicein anaws_instancethe encrypted option is completely ignored. This PR should fix that issue. I branched off ofv0.4.2. I'm not sure what the proper protocol is for you guys, but I figured the change is small enough that it can be moved around and updated easily if we need to merge in the latest code. I just figured it'd be something for av0.4.3.All associated tests have been run.