Skip to content
This repository has been archived by the owner on Mar 3, 2021. It is now read-only.

TODO #1

Closed
7 of 20 tasks
randomcamel opened this issue Oct 18, 2015 · 1 comment
Closed
7 of 20 tasks

TODO #1

randomcamel opened this issue Oct 18, 2015 · 1 comment

Comments

@randomcamel
Copy link
Owner

  • Allow user to specify :plan vs. :apply and make that useful.
  • Integration testing (e.g. actually running the terraform_execute resource).
  • Package up for consumption.
  • Full and unit-tested top-level provisioner support.
  • Full and unit-tested top-level module support.
  • More terraform subcommands as resource actions. Possibilities:
    • destroy - Destroy Terraform-managed infrastructure
    • get - Download and install modules for the configuration
    • graph - Create a visual graph of Terraform resources
    • init - Initializes Terraform configuration from a module
    • output - Read an output from a state file
    • push - Upload this Terraform module to Atlas to run
    • refresh - Update local state file against real resources
    • remote - Configure remote state storage
    • show - Inspect Terraform state or plan
    • taint - Manually mark a resource for recreation
  • Better/any .tfstate management.
  • Build some verified real-world examples.
  • Make sure we can do the nested hashes of e.g. AWS Security Groups.
  • Make it run outside Chris's environment of having both Docker and AWS configured.
randomcamel added a commit that referenced this issue Oct 18, 2015
@randomcamel
Copy link
Owner Author

Toy project, EOLing since no one uses it. =)

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

1 participant