__acl: remove deprecated parameters #43
Labels
No Label
bugfix
cleanup
discussion
documentation
doing
done
feature
improvement
packaging
Stale
testing
TODO
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ungleich-public/cdist#43
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ander Can you remove
__acl
deprecated parameters and prepare MR?In the ++minor we will remove them.
mentioned in commit
f96f23e970
closed via merge request !933
mentioned in merge request !933
sigh, time flies. sorry for taking this long, I have no excuse but laziness 👹
but take a look at !933
@ander Is it feasible that you do this in a week or two?
This question came up when I suggested "cdist-museum" for old and deleted types in cdist core. @poljakowski raised the question if this should also apply to the deprecated parameters in
__acl
.IMO: If no use case breaks and it's just a matter of switching from one parameter to another, there is no reason to archive the old version.
currently backwards compatibility does exactly that - maps deprecated parameters to
--entry
and also emits warning.I think we have waited long enough.
I'll deal with this after dance around
__download
and__unpack
ends in one way or another.I'm continuing the discussion of !899 here, because it doesn't really fit there.
I don't know POSIX ACLs well, but I'm wondering if all previous use cases of the deprecated parameters could be mapped to a new
--entry
parameter?If not, which cases do not work anymore if the deprecated parameters are removed?
mentioned in merge request !899