New ephemeral resource cloudint_config - #407
Open
chpag wants to merge 7 commits into
Open
Conversation
….yaml new file: examples/ephemeral-resources/cloudinit_config/ephemeral-resource.tf new file: examples/ephemeral-resources/cloudinit_config/hello-script.sh new file: internal/provider/ephemeral_resource_cloudinit_config.go new file: internal/provider/ephemeral_resource_cloudinit_config_test.go modified: internal/provider/provider.go new file: templates/ephemeral-resources/config.md.tmpl
modified: templates/ephemeral-resources/config.md.tmpl
modified: templates/ephemeral-resources/config.md.tmpl
modified: internal/provider/ephemeral_resource_cloudinit_config_test.go
This file contains hidden or 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
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.
Related Issue
Closes #396
Description
This PR implements an ephemeral resource version of cloudinit_config that enables secure handling of sensitive data (such as secrets from Vault) in cloud-init configurations without storing them in Terraform state.
When released, it would required to add a Write-Only attribute for user_data on different providers (aws, azure, gcp, vsphere, ...) to handle ephemeral cloudinit_config resource
Rollback Plan
Changes to Security Controls
No Change
Output from Acceptance Testing