enable the possibility to decide which policy to use with semantic versioning

[lucamaf]

At the moment when somebody runs the ansible playbook and the version change is minor, the old service is subscribed and when instead the change is major a new service is created.
Some customers prefer to decide this behavior, for example by having every version overwrite the previous or having new services even for minors. Would be nice to have a variable to manage this.

[nmasse-itix]

Hi @lucamaf !

Thanks for the feedback. Customers can already use their own versioning scheme with the ansible playbook:
https://github.com/nmasse-itix/threescale-cicd/blob/master/CUSTOM.md#override-the-default-versioning-scheme

Let me know if it works for your customers.

[lucamaf]

great, didn't know that!

…

On Tue, Apr 23, 2019 at 3:21 PM Nicolas MASSE ***@***.***> wrote: Hi @lucamaf <https://github.com/lucamaf> ! Thanks for the feedback. Customers can already use their own versioning scheme with the ansible playbook: https://github.com/nmasse-itix/threescale-cicd/blob/master/CUSTOM.md#override-the-default-versioning-scheme Let me know if it works for your customers. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#51 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANFTIZ25MBOT4UO34GLOE3PR22ITANCNFSM4HHFB4TA> .