Deleting a budget that is associated with a policy may also result in the deletion of the associated policy.
search cancel

Deleting a budget that is associated with a policy may also result in the deletion of the associated policy.

book

Article ID: 446907

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

During testing, the following behavior was observed:

  1. Two test budgets, chtest1 and chtest2 were created.
  2. A policy named budgetpolicytesting was created.
  3. Two separate policy blocks were configured with each block referencing one of the budgets.
  4. When the chtest1 budget was deleted, a confirmation prompt appeared stating that the deletion would impact associated objects and explicitly referenced the budgetpolicytesting policy.
  5. After confirming the deletion, the budgetpolicytesting policy was no longer available.

Cause

The policy has a direct dependency on the budget. Deleting the budget removes the dependency and the platform consequently deletes the associated policy after user confirmation.

Based on the warning message, it appears to be expected product behavior. The confirmation dialog explicitly informs the user that associated objects (including the policy) will be impacted and proceeding with the deletion confirms acceptance of that action.

Resolution

 

  • Before deleting a budget, review the confirmation prompt carefully, as it identifies any associated objects that will be impacted.
  • If the associated policy needs to be retained, avoid deleting the budget until the dependency has been reviewed or removed.