Fix akeyless bug that prevents releases and release failed build

[arthurgousset]

Hey @pputman12, the automatic release flow in this repo celo-org/rainbowkit-celo seems to have broken at the "Akeyless Get Secrets" step.

Error: can't get secret value: %!w(string={"error":"failed to get the value of the requested secrets: Desc: failed to obtain secret access credentials, Error: Desc: Failed to get secret access creds. Status 401 Unauthorized, Error: UnauthorizedAccess. Message: account id: acc-2gyt10uq3as8, access id: p-kf9vjzruht6l. unauthorized access for access id p-kf9vjzruht6l"}
)

Probably a relatively simple permissions issue. Could you help me fix the bug?

Priority: Not urgent, I'd say in the next 1-2 weeks is fine. The only impact this has is that a demo website (at rainbowkit-with-celo.vercel.app) cannot be deployed in the mean time. I made a small patch that failed to be deployed here:

• Fix maxFeePerGas bug in example app #103

[arthurgousset]

Fixed by:

• fixing key path #100

[arthurgousset]

I'm not sure this is fixed @pputman-clabs, the workflow related to the PR broke:

• https://github.com/celo-org/rainbowkit-celo/actions/runs/7742517634

Or am I missing something?

[pputman-clabs]

No this is due to the branch restriction I setup which apparently isn't working. fixed now, I'll figure out whats wrong with the subclaims.

[arthurgousset]

Hey @pputman-clabs the same "Akeyless Get Secrets" step is broken in the celo-org/developer-tooling repo.

For example, this workflow in this PR:

• Updates CONTRIBUTING.md developer-tooling#93
• https://github.com/celo-org/developer-tooling/actions/runs/7744610057/job/21118722738

[pputman-clabs]

Access role was overwritten, fixed now.

[pputman-clabs]

To document the issues, we recently added a branch protection so only certain branches would be able to access the secret.

This adds a branch=main subclaim to the access role. This seems to have caused a problem where its not actually allowing the specified branch, so I've removed that restriction. I'll have to retest and see what subclaims the OIDC token is sending from github, to see why its not matching and running properly.

[arthurgousset]

Thanks for the context, very useful 💯

[arthurgousset]

This PR fixed the release workflow, since the subsequent workflows ran without errors.

For example:

• Merge pull request #100 from celo-org/pputman/update-key-path #28
• extend base developer tooling renovate config (#109) #29

On that basis, this ticket can be closed.