Support creating catalogdb for xray when using internal postgres at the jfrog-platform level
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 288
- Forks
- 471
- Avg merge
- 18h 11m
- Merged PRs (30d)
- 54
Description
The xray catalog-db-create-hook currently only is created if the internal postgres is deployed from the xray chart. But if deploying xray with the frog-platform chart with an internal postgres at that level, the catalogdb never gets created. Would like to deploy jfrog-platform with an internal postgres and have a way to automatically create the catalogdb for xray
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
Start by tracing the xray catalog-db-create-hook and how the jfrog-platform chart configures internal PostgreSQL. Compare the hook conditions when PostgreSQL is deployed by the xray chart versus at the platform level. Done means deploying jfrog-platform with platform-level internal PostgreSQL automatically creates Xray's catalogdb.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100