Support account-level secrets across functions
Open
Nobody has claimed this yet.
roadmap
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
Allow an account administrator to define secrets once at account scope and make them available to functions in that account. This avoids duplicating common credentials in every function configuration.
Definition of Done
- An administrator can create and update account-level secrets.
- Functions in the account can consume those secrets through the supported NVCF secret delivery mechanism.
- Function-specific secrets can continue to be configured independently.
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 locating the account and function configuration entry points and the supported NVCF secret delivery mechanism. Trace how administrators currently configure function-specific secrets, then verify that account-level create/update, function consumption, and independent function-specific configuration are all covered by the definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100