Have a default instance config for rapid deployment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 19
- Forks
- 10
- Avg merge
- 6d 9h
- Merged PRs (30d)
- 6
Description
TL;DR
Deploy an AuraDB instance without that pesky button pressing
Description
For those who frequently deploy, use and then delete AuraDB instances, having to enter all of the required parameters for provisioning is painful. Allowing a 'default' configuration to be defined and then referenced for AuraDB creation would make that easier.
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 with the CLI command that creates an AuraDB instance and trace how its required provisioning parameters are currently supplied. Determine how a default configuration could be defined and referenced during creation. Done means users can deploy an instance without repeatedly entering the same parameters, while preserving a way to override them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100