splunk / splunk/vault-plugin-secrets-gitlab
Templated policies
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 62
- Forks
- 12
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Hi there,
Having the project_id in parameter does not allow to leverage templated policies.
Any simple way to provide the projet_id in the path and have the ability to use templated policies ?
( Aside from creating one role per project ;) )
Regards,
-- Regis
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
Start by tracing how project_id is currently accepted as a parameter and how the plugin handles templated policies. Determine whether project_id can instead be supplied in the path while preserving templated-policy support; done means a documented, tested approach that avoids creating one role per project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100