Templated policies
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
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.
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
- Dominant language
- Go
- Stars
- 63
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from splunk/vault-plugin-secrets-gitlab
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
splunk/vault-plugin-secrets-gitlab#117 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
splunk/vault-plugin-secrets-gitlab#111 · 1 comment ·
-
support for group level access tokenPossibly taken @M0roSan claimed this 1701 days ago. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
splunk/vault-plugin-secrets-gitlab#36 · 6 comments · 1 reaction ·
-
documentation help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in splunk/vault-plugin-secrets-gitlab
Similar issues
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-go#2124 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
evener-transcript-v2-upgrade tool still scans transcript files through bufio's 4 KiB default bufferOpen
Difficulty 1/5 Under an hour Newbie friendliness 78/100
prime-radiant-inc/evener#6370 ·
Maintainers usually reply within 1 day
-
ManageSieve proxy: a backend's NO/BYE greeting is skipped as a capability line and reported as EOFOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 65/100