Managing Github Actions

There are at least couple of reusable github action (also known as workflow) repositories in Gjensidige's ecosystem. However, sometimes you just need to implement one of your own. Depending on the project you're at, you might run into issues where your workflow is not being taken by the workers or you're unable to authenticate to Azure. That's what this article aims to address.

What's your prefix?

Depending on the repository and therefore repository template, you might have a certain set of permissions out of the box.

You should investigate this repository and find out whether and where your repository is referenced.

If you're on a dbt project, it's likely that your repository permissions are defined in team_bi-data-analytics and therefore you're only able to run Github Actions defined in the dbt-reusable-workflows

Projects that deploy static docusaurus websites, such as this one, can usually run their own workflows, but only after the workflows are merged into main. Sometimes that's not ideal and it can be modified, by removing the constraint of "refs/heads/main" on this line in this particular example.

The team_bi-data-science.tf contains all kinds of interesting combinations, so it's the one we prefer to employ when testing/running custom workflows.

For example, you might want to do some additional magic in your dbt project, in which case, you'd need to do a PR similar to this-one. Once it's merged (and the pipeline goes through with Terraform Apply) - you should be able to run the Github Action of your choice directly from the branch in progress instead of having to merge.