Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate terraform plan with cloudformation changesets #6014

Closed
torfredrik opened this issue Apr 5, 2016 · 5 comments
Closed

Integrate terraform plan with cloudformation changesets #6014

torfredrik opened this issue Apr 5, 2016 · 5 comments

Comments

@torfredrik
Copy link

When a cloudformation stack is changed in terraform the terraform plan only shows a change to the stack, it would be useful to know the underlying resource changes that will occur. An easy way to add this feature is using cloudformation change sets .

@chenrui333
Copy link

chenrui333 commented Sep 25, 2016

That would be a nice feature.

@apparentlymart
Copy link
Contributor

Seems like a potential use-case for #8769, though it doesn't fit all that great with my current framing of the problem since it looks like a CloudFormation changeset is a first-class object whose lifecycle ought to be managed, rather than just something we can create during plan and then leave dangling.

@torfredrik
Copy link
Author

That is correct, cleaning up the change set after a plan should be the way to go about it.

@lorengordon
Copy link
Contributor

That is correct, cleaning up the change set after a plan should be the way to go about it.

That seems wrong to me... if you create a changeset in the plan, then you should execute the changeset in the apply.

@ghost
Copy link

ghost commented Apr 3, 2020

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 ghost locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants