bug: oci cli doesn't respect delete protection lock set by terraform oci provider
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
when creating comparting using terraform oci provider resource, oci_identity_compartment, there is a default enable_delete = false setting to protect the compartment from being deleted. However, with the default setting, terraform cli cannot delete the compartment, oci cli doesn't respect the setting and still can delete the compartment.
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 with the OCI CLI compartment-delete command and the Terraform OCI provider's oci_identity_compartment resource, focusing on the enable_delete = false setting. Reproduce the behavior with a protected compartment and verify that the CLI honors the protection and refuses deletion when it is disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, terraform
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100