Invert deletion / creation process

[BitProcessor]

Recently changed some stuff around where I went from type: application to type: kafka-streams. That - of course - lead to a bunch of ACL creation and deletion events, which ran just fine, nothing to remark there.

However, and I am assuming this is the case for the entire application, the deletes happen before the creations and that caused an issue that - I think - could be avoided:

Due to the order described above, applications temporarily lost access to certain topics resulting in errors. I think this could have been avoided if the ACL creation of the new rules would have happened before the deletion of the old rules?

Would it be a good idea for a future version to switch the order around? Or is there a reason why this is implemented as such?

[BitProcessor]

@marcellorego ^^^

[taislapta]

would be nice to have --target if I like to delete only specific ACL