puppetlabs / puppetlabs/puppet-resource_api
Deletion of resources with dependencies
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 27
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Bug
When a manifest is crafted that asks for a child resource to be deleted before its parent resource, puppet will allow this to occur. The provider may then run into an issue where this will fail because the parent resource still exists.
Expected Behavior
As both resources have been flagged for deletion then the order in which they are defined in the manifest should not have an effect on the outcome. The parent should be deleted first followed by the child.
Additional Context
Originally filed as https://tickets.puppetlabs.com/browse/PDK-1136 by @da-ar
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 by tracing how the library determines deletion order for dependent resources; the issue does not name an entry point, file, or test. Reproduce a manifest that lists a child before its parent, then verify that deletion consistently removes the parent before the child without provider failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100