ovh / ovh/public-cloud-databases-operator
[ENHANCEMENT] ✨ ServiceID and projectID are not coherent with the OVHcloud Terraform provider
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 9
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 5
Description
For the operator the service id is the DB uuid and the project id is the OVHcloud public cloud project uuid.
In the OVHcloud Terraform provider to create a database the service id is the OVHcloud public cloud project id and the cluster_id is the DB uuid (https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_database_postgresql_user).
I think it's confusing when we use both of tools (operator and terraform).
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 by comparing the operator's ServiceID and projectID semantics with the OVHcloud Terraform provider resource documentation linked in the issue. Trace how the operator represents the database UUID, cluster_id, and public cloud project UUID, then define completion as consistent identifier naming and usage across both tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, terraform
- Domain
- cloud, databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100