`oci_env db reset` is recreating the database with a different user than expected
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 39
- Avg merge
- 18d 18h
- Merged PRs (30d)
- 1
Description
https://github.com/pulp/oci_env/blob/main/base/container_scripts/database_reset.sh#L9
The use of --user postgres is creating the db differently than originally by the oci container.
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 base/container_scripts/database_reset.sh at line 9 and inspect how oci_env db reset invokes the database reset. Compare the --user postgres behavior with how the OCI container originally creates the database. Done means the reset recreates it with the expected user; no test file is mentioned in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, shell
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100