bytebase / bytebase/terraform-provider-bytebase
The provider doesn't show the data_sources diff on the bytebase_instance resource.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 10
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 5
Description
We are facing trouble with bytebase_instance resources, as the diff is not showing on plan and apply:
~ resource "bytebase_instance" "instances" {
id = "instances/xxxxx-xpto"
name = "instances/xxxxx-xpto"
# (10 unchanged attributes hidden)
- data_sources {
# At least one attribute in this block is (or was) sensitive,
# so its contents will not be displayed.
}
+ data_sources {
# At least one attribute in this block is (or was) sensitive,
# so its contents will not be displayed.
}
}
Since the data_sources block is marked as sensitive, all information is hidden. Is it possible to modify the provider to display the differences while still concealing only sensitive attributes?
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 locating the bytebase_instance resource schema and its data_sources block in the provider. Trace how sensitivity is assigned and how Terraform renders the plan, then check existing provider tests if available. Done means non-sensitive data_sources differences appear in plan and apply output while sensitive attributes remain concealed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100