Altinity / Altinity/terraform-provider-altinitycloud
force_destroy, force_destroy_clusters, skip_deprovision_on_destroy are set to null in data source
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
left one is the env data retrieved from data source, right one is the tfstate file of the created environment. all three variables are set to true (zones is different issue), but null is returned.
as Nacho explained these properties are not stored in the db, which is an issue, because customer cant possibly have any idea why data source is returning the null value.
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
Trace the data source handling for force_destroy, force_destroy_clusters, and skip_deprovision_on_destroy, then compare the returned environment data with the Terraform state shown in the report. Done means these configured true values are returned by the data source instead of null, with coverage for the behavior if the repository has relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100