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

lifecycle: run once #3088

Closed
failshell opened this issue Aug 27, 2015 · 4 comments
Closed

lifecycle: run once #3088

failshell opened this issue Aug 27, 2015 · 4 comments

Comments

@failshell
Copy link

It would be nice if we could flag resources as run once. The behaviour would be for Terraform to create the resource and then don't update it if it notices it's been change.

Let me give you a use case for it. We have a primary and secondary VPN network between our VPCs. Custom routes are added to our route tables for the primary. But in we sometimes switch to our secondary VPN network for maintenances for example. Problem is, we do that with a CLI tool we wrote. As it's faster than fetching our TF repo, making a change, and then applying that change. Our tool allows us to switch routes rapidly. But if someone in our teams isn't aware of that change for some reason, and runs TF, it will revert our routing back to the primary. Might not be good.

@KoeSystems
Copy link

+1

@phinze
Copy link
Contributor

phinze commented Oct 12, 2015

Yep - the use case makes sense. Closing this to consolidate around #2018

@phinze phinze closed this as completed Oct 12, 2015
@akamalov
Copy link

Pardon my ignorance, was runOnce feature ever implemented? Thanks so much in advance!!

@ghost
Copy link

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

No branches or pull requests

4 participants