Juan Vela

Nevermind. I discovered this can be done natively from the workflow itself by using https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes

@WyriHaximus in fact, for my case what I want/need is to fail after some time. As an example: for stuck CI stuff I don't want to waste runner minutes, but...

FYI: I can confirm the native timeout results in failure

@WyriHaximus as I said, for my use-case the native way is just enough. However, I believe making those 2 parameters configurable will work for mostly all (if not all) use-cases

This project concept is very interesting to group workspaces that share a common purpose. As an example, I use the project concept to group all the environments and regions (one...

Just to provide some TFC context: While it's true the lock reason is displayed in the TFC UI when you navigate to Locking section, it's displayed nowhere else. As @alfespa17...

A good reason to implement this is to be able to use the workspace name within the code by using `terraform.workspace`. While in TFC we were able to use that...

> Hello @juan-vg when you setup a CLI driven workflow in TFC and you want to the `workspace new command` you will get the following error, not sure how you...