There is no way to remove a Directive based on a Technique that no longer exists
I tried to update my Techniques, but in the process also removed a Technique that was here before (a custom one).
Problem is, the deployement does not work anymore, and I can not remove the Directive that breaks it as there is no more a Delete button :)
Please see the attached screenshot.
#2 Updated by Matthieu CERDA over 3 years ago
For me, the error under "About this Directive" is relevant and needs to stay. However, the message at the botton is meaningless for an end user, duplicates what is "nicely" said in the upper one and should maybe be replaced by a "migrate to another version or delete" choice :)
I did not verify if the same problem happens if there is another version available for this Technique, the behavior might not be the same ?
#3 Updated by François ARMAND over 3 years ago
- Priority changed from 2 to 4
I think I agree with the qualification.
I'm not sure where the error message should go, but clearly, we have to provide the user with a way to get out of that situation (without relying on any LDAP/cmd line wizardry).
The very first step seems to let the promise generation process runs even in that case. We could for example disable directives with broken techniques.
The second step is to allow to delete the directive. Migration would be nice but may be more difficult.
The good news it that there is a simple workaround: just revert the commit that removed the Technique, then reload Techniques library, then delete Directives based on the Technique, the delete back the Technique.
I lowered the priority to 4 because 1/ it is not a really frequent use case and 2/ the workaround is simple.
#47 Updated by François ARMAND 5 months ago
- File 2017-10-18_18.24.04-Rudder_-_Directives_Management.png added
- File 2017-10-18_18.52.41-Rudder_-_Directives_Management.png added
The proposed change allows to delete a Directive when no version of the technique is availabe at all:
When at least one version of the technique is available, a migration towards it is done with that warning message:
#55 Updated by Vincent MEMBRÉ 5 months ago
- Status changed from Pending release to Released