bytebase / bytebase/terraform-provider-bytebase
ssl_ca is ignored for bytebase_instance.data_sources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 10
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 5
Description
Configuring the CA certificates for RDS instances does nothing to get them configured. Have to use the web UI to add them.
Example:
resource "bytebase_instance" "my_dev_instance" {
resource_id = "my_dev_instance"
title = "my_dev_instance"
environment = bytebase_environment.dev.id
engine = "POSTGRES"
list_all_databases = true
data_sources {
id = "admin-conn"
type = "ADMIN"
host = "my_dev_instance.dk2lk3430se.us-east-2.rds.amazonaws.com"
port = "5432"
username = "bytebase"
password = "*******"
ssl_ca = file("${var.aws_region}-bundle.pem")
}
}
Even if I delete the existing connection info in the UI and rerun terraform it will be recreated but without the CA certs.
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 how the bytebase_instance resource handles data_sources and the ssl_ca attribute during Terraform apply. Reproduce the example configuration, then verify that the resulting connection includes the CA certificate rather than requiring the web UI; done means the configured CA is preserved after recreation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100