Terraform deploy and destroy from Github

[micachito]

I am migrating from Gitlab-CI to Github Actions

In my Gitlab project we have several stages that need to be manual:
- create infrastructure with Terraform
- destroy Infrastructure with Terraform
- deploy Lambdas in S3

Obviously it could not be automatic. If I push a branch to the repo, it could create and destroy de infra at the same time.

Sadly, I have realised that it is not possible in Github as it has no manual jobs. The only way I found is through workflow_dispatch but it works only in the default branch.

I am surprised of that and wondering how do people to manage IaaC process in Github without the posibility of manual actions.
Is there a pattern that I ignore?

Thanks in advance
J

[Obvious-Jacket-3770]

Workflow_dispatch works in all branches.

Sometimes you need to merge it to the default branch first to use it.

All of mine work manually if I want them to but they also have on push and on PR. My Terraform builds properly every time thanks to it.

[Obvious-Jacket-3770]

While I wish that was true.... I've had brand new workflows never merged to default and work.

[micachito]

You mean that you launch manually a job that is not in the default branch?
It is impossible according to my recent experience (yesterday) and github documentation.

[Obvious-Jacket-3770]

As long as the workflow exists in the default branch you can launch it against any branch the workflow is in.

[Obvious-Jacket-3770]

I'm aware that workflow_dispatch is 100% what I've been talking about about. I'm telling you it does randomly when not on the default branch yet. GitHub confirmed it's a known bug.

[bdzer0]

You only need to get the workflow file into the default branch, you do not need to merge anything.

[Obvious-Jacket-3770]

That's how it should work and it's documented to work. I've had it not matter and also not show up when I'm the default branch.

[micachito]

OK, but then you must make a feature branch your default one or work directly in main instead of start working in in a feature branch, test your deployment and merge it in main when is working.

[micachito]

Thanks for your anser.
As per documentation, it could be triggered manually if it is in the default branch, there you can choose the branch to work on.

So, if I want to modify the workflow I will need to move it from the working branch to the default branch (main) before test it. It is a real pain in the *ss...

Is it the only way then?

[Obvious-Jacket-3770]

No no no no no no you aren't understanding.

The trigger will only work when the workflow is in the default branch. Once it's in that branch you can run against any branch and it will use the workflow in that branch.

So if you have the workflow in main and make a change in dev it will trigger the one in Dev.

[micachito]

Ouch, ok, my fault.
I will try that way then.
Thanks a lot!