Configure Action access for OCI chart push

[jkroepke]

Currently, pushing charts to Github packages fails, because the authorization is not etablish between Github Packages and Github Action.

In order to allow pushing packages via GITHUB_TOKEN, an admin needs to permit this repository on Github Packagess.

See: https://docs.github.com/en/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token

Ref: #2443, #2474

[mhoyer]

The issue is still there. Is there anything we can support here?

https://github.com/grafana/helm-charts/actions/runs/7031694843/job/19133854192#step:7:13

[jkroepke]

@mhoyer yes!

A Grafana member with repository permission (i guess admin) has to configure the setting that actions have access to package in general.

https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility

[jsclifford]

I would like to request OCI support be added as hashicorp/helm terraform provided requires OCI publishing of charts. I am using the grafana/k6-operator helm chart.

[jkroepke]

@jsclifford

terraform fully supports traditional helm repositories. Reading the docs (https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release), the first example is using a traditional helm repository.

Maybe you are hitting this issue: hashicorp/terraform-provider-helm#707

[jsclifford]

@jsclifford

terraform fully supports traditional helm repositories. Reading the docs (https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release), the first example is using a traditional helm repository.

Maybe you are hitting this issue: hashicorp/terraform-provider-helm#707

Looks like I am. Thanks. Going down the rabbit hole on this error. Jumping from one issue to another.