stackabletech / stackabletech/superset-operator
Special characters in database password don't work
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 10
Description
Affected version
0.5.0
Current and expected behavior
When using a password for accessing the database that contains special characters (in this case it was @ , but others may be problematic as well) the job that initializes the database fails and Superset is never started.
Expected behavior, passwords should work regardless of which characters they contain. Also, users should not be required to escape any characters in the passwords (except maybe if they create issues with yaml).
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
No response
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
The payload names no file or test; start by reproducing database initialization with a password containing @ and inspect how the operator passes that password to the database setup. Done means initialization succeeds and Superset starts without requiring users to escape password characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100