Add workflow for deploying to staging

[Matt-Yorkley]

What? Why?

Adds a new workflow for deploying to staging servers via github actions.

What should we test?

The funny thing about workflows is you can't see if they work until after they're merged...

It should be possible to trigger a deployment by either:

• adding the pr-staged-uk or pr-staged-fr or pr-staged-au label to a pull request
• going into Actions then Workflows and selecting the workflow and then manually triggering a deployment (and it should let you choose a branch and a staging server)

Release notes

Changelog Category: Technical changes

The title of the pull request will be included in the release notes.

[mkllnk]

Very cool. Thank you.

[jibees]

Do you know why I can't see the box with CI which should be at the bottom of a PR page ?
I can't see on this PR, and some others, as I can see it here : #10704

I mean this box:

[Matt-Yorkley]

That's pretty weird. It was there last night when I went to bed, and now it's gone. Maybe a temporary github glitch? 🤷‍♂️

[filipefurtad0]

Could this be related? Should we empty our GH Actions cache?

[sigmundpetersen]

I think it goes away when PR is merged, no?

[filipefurtad0]

I think it goes away when PR is merged, no?

Yes, I think so @sigmundpetersen 👍

Thanks for this change @Matt-Yorkley 🙏

I'm playing around with the basic functionalities, some initial thoughts:

• The label process is quite straightforward. But somehow is failing with:

ofn-deploy@staging.coopcircuits.fr: Permission denied (publickey).

Or for staging-UK, an example here:
https://github.com/openfoodfoundation/openfoodnetwork/actions/runs/5288835468/jobs/9571186050

• And the manual process:

and it should let you choose a branch and a staging server

Worked nicely for master, which can be found under Branches 👍
We might need to adjust out release process, as I could not find a "build" for the different versions of master. But I think we can circumvent this by creating a "release branch" - something to discuss.

However, I think we're only able to select some branches - or am I looking in the wrong place? For example, I'm not finding a way to trigger a manual deploy on mkllnk:ruby3.1, other than the label process.

Also, we can see the Tags from previous releases, which is great 💪

[Matt-Yorkley]

Yeah the UX around Github Actions seems a bit clunky. And yes it's currently not working with the labelling thing, I need to tweak it a bit and figure out why. It seems like maybe it's ignoring the secrets in some cases and not others?

Also it looks like when manually triggering a deployment it only works if the branch you're choosing already contains the new workflow(?), which is a bit annoying. So it's currently present in master but it's not in last week's release, so I think we can't deploy last week's release to staging via the workflow, but maybe we can do it with the next release?

I'm not finding a way to trigger a manual deploy on mkllnk:ruby3.1, other than the label process

Yeah I think we'll want to deploy the merge commit for PRs in that case instead of the branch in the external repo (which should work with the labelling-trigger on pull requests, once they're fixed).

It's getting there but it's not finished yet 👍