Allow local runs

[wonko]

Feature description 💡

While developing new/experimental/poc/... infrastructure, it is not always easy to work through the cycle of committing and running remotely all the time. It would be good to allow a flow to run locally (and then push the state to terrakube). Iterations go much faster, not all code might end up in the project, or some infrastructure will even be destroyed before the code is ready for inclusion in the project....

(Terraform cloud has the concept of "speculative plans" for this (where only the plan phase is allowed, the apply still has to be done through the cloud platform). This is not 100% equal, and only works in limited scenarios. )

Anything else?

No response

[alfespa17]

We added that feature in this PR

#644

You can trigger a plan using the CLI driven workflow in a VCS connected repository

[wonko]

It still runs the code in the executor, without my local changes (uncommitted).

There are two alternatives in terraform cloud:

• local execution mode, runs the terraform just locally, and only uses the cloud platform as state store (see https://developer.hashicorp.com/terraform/cloud-docs/workspaces/settings#execution-mode)
• speculative plans, where the content of the current folder is sent to the executor, instead of relying on the VCS. See https://developer.hashicorp.com/terraform/cloud-docs/run/cli#remote-speculative-plans

[alfespa17]

There is an option in the workspace setting you need to change that to local,

You can check here:

#451
#455

After changin that to local you just need to run terraform init again to make it work

[wonko]

Right, looked right over that ... You might want to add this to the creation of the workspace and/or make it somehow a default on the workspace (for implicit created workspaces).

Thanks for the help!

[dcopestake]

I've just raised #758 as a feature request for default execution mode 👍

[jcanizalez]

I created a PR #764 to add a default execution mode at organization level