[#GALAXY-65] Determine appropriate action when enabling a policy and not all artifacts in that lifecycle/phase meet that policy

Galaxy

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

Created: 28/Jan/08 10:38 AM Updated: 22/Feb/08 01:04 PM

Component/s:

Core

Affects Version/s:

1.0-beta-1

Fix Version/s:

1.0-beta-2

Time Tracking:

Not Specified

Labels:
User impact:	Medium

Description

« Hide

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?

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 28/Jan/08 10:41 AM

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.

[ Permlink | « Hide ]

Dan Diephouse added a comment - 28/Jan/08 10:52 AM

Sounds good to me.

[ Permlink | « Hide ]

Dan Diephouse added a comment - 22/Feb/08 01:04 PM

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