Determine appropriate action when enabling a policy and not all artifacts in that lifecycle/phase meet that policy

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: To be reviewed To be reviewed
  • Resolution: Fixed
  • Affects Version/s: 1.0-beta-1
  • Fix Version/s: 1.0-beta-2
  • Component/s: Core
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

Lets say I enable a policy on workspace and lifecycle phase. If there are artifacts in that workspace/phase which do not meet the required policy, what should happen? Should we:
1. Not allow the policy to be enabled until artifacts meet that policy?
2. Allow the user to take corrective action, but let it be?
3. Other?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment -

IMO, it should fail to apply, programmatic call may not have an option to take a corrective action, though we could prompt the client with a 'recoverable' exception subclass.

Show
Andrew Perepelytsya added a comment - IMO, it should fail to apply, programmatic call may not have an option to take a corrective action, though we could prompt the client with a 'recoverable' exception subclass.
Hide
Permalink
Dan Diephouse added a comment -

Sounds good to me.

Show
Dan Diephouse added a comment - Sounds good to me.
Hide
Permalink
Dan Diephouse added a comment -

This was fixed in beta-2. We don't allow the policy to be applied if the artifacts don't meet the policy.

Show
Dan Diephouse added a comment - This was fixed in beta-2. We don't allow the policy to be applied if the artifacts don't meet the policy.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: