Provide an interface to job level settings
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 199
- Forks
- 67
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 3
Description
There are some settings that are impossible to set with this action. In particular we have a private AWS ECR docker registry that we log in to using the recommended OIDC method so that we can generate a short-lived CI specific token.
Part of this process requires setting the permissions: id-token: write setting on the job, or the GH token will not have enough permission to accomplish its task. This leaves us in a situation where we either have to abandon the use of this plugin, or abandon the use of OIDC. As an ops professional, I would lean toward the former, but some of our developers would probably prefer to keep using this plugin, so I would just like to request that you offer some sort of interface to this.
If you want to scope it just to permissions that's fine, but I'd prefer something a bit more generic to set any other settings that a job might want, that are currently unsettable by this generator.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing how this Scala sbt plugin generates GitHub Actions jobs, then determine where job-level settings and permissions could be represented; done means users can configure the requested OIDC permission or broader job settings and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, scala
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100