3 ms·
Yeah, moving objects around the config is common if you want to keep it organized and requires manual actions that require essentially a global lock on the stac
by kevincox 5y ago
Yeah, moving objects around the config is common if you want to keep it organized and requires manual actions that require essentially a global lock on the stack (and Terraform has no built-in feature to actually take this lock). It makes it basically impossible to implement a fully automated production change pipeline with Terraform.
- cormacrelf 5y agoMoreover I can never, ever, remember the syntax for moving objects around the config. It's really painful. Edit: the aliases would have to handle moving as well as renaming. You could just have aliases in a global namespace, which means adding `alias = "portable-elb"` and doing one `terraform apply` means you can pick up that config, drop it anywhere else, and it will move it for you. It wouldn't even need to do a full `apply`, just a local JSON manipulation.