Open myllynen opened 6 months ago
so this isn't a bug this would be a change in how the role works itself, I am updating the labels to fit
I'm not sure about the labels and classification but the hope here is that the role would be idempotent. Thanks.
With a local automation hub and collection version 2.0.6 + PR 386 using the following with the needed namespace created earlier the publish role works on the first run but fails on the second run:
Looks like the role does not detect that the collection version already exist and then needlessly clones it, builds it, and tries to upload it. This causes issues with CaC/GitOps where ideally there could be only one yml file listing collections and collections could be updated individually as new versions become available. Thanks.