Confirmation step for production
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
It might be nice to optionally have some sort of guard rail or required confirmation step for production migrations. I typically use `ctrl+r` to get my migrate command from my shell history. It is too easy to accidentally get and run the production migrate command when wanting to migrate development.
It would be nice to have a confirmation step that required typing the name of the environment.
This could be toggled in the config files locally or with a special table remotely. Local config might be simpler, but it could be more difficult when deploy target is determined by environment variable or program argument. Also, if it was a remote table it could not be bypassed as easily.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Begin by locating the production migration command and its configuration handling, then clarify whether the project wants local configuration or a remote safeguard; done would mean an optional production confirmation requiring the environment name without hindering development migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100