wso2 / wso2/open-cloud-datacenter
Expose harvester_api_server URL from harvester-integration module
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 19
- Forks
- 15
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 4
Description
Summary
The harvester-integration module already parses the Harvester kubeconfig and extracts the cluster server URL into local._matched_cluster.cluster.server (used internally to build the SA kubeconfig). Exposing this as an output removes the need for consumers (e.g. 08-workloads) to hardcode the Harvester VIP address when calling harvester-cloud-credential.
Change
Add harvester_api_server output to modules/management/harvester-integration. Marked sensitive = true because it derives from the sensitive harvester_kubeconfig input. Returns null when create_cloud_credential = false.
Closes #57
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
Inspect the harvester-integration module under modules/management/harvester-integration, starting with local._matched_cluster.cluster.server and the harvester_kubeconfig input. Add the harvester_api_server output with sensitive handling and the documented null behavior when create_cloud_credential is false. Verify that consumers can use the output instead of hardcoding the Harvester VIP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100