Support pulling token from secrets management for service overrides.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 35
- Forks
- 35
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 8
Description
Describe the Enhancement:
I would like to store secrets related to Automate in a secure form. Today, I can override service values directly, build with the secret in, or put a user.toml down with my token in plain text.
I'd like a way to pull those secrets from a secure location like a secrets management solution.
Describe the Need:
Keeping secrets out of plain text on systems is pretty standard security best-practice. All users would benefit from being able to keep secrets out of source code, plain text in env variables, and not stored in plain text on disk.
Current Alternative
Right now, the best workaround I've found involves using the Habitat cookbook to pull the secret out of secrets management, and using that to put the Automate info into a user.toml file.
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 locating how service overrides and user.toml are handled, then review the referenced Habitat cookbook workaround; done would require a defined, secure mechanism for pulling Automate secrets without storing them in source, environment variables, or plain-text files.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100