[Ansible-service-broker] Tagging before 3.7

[John Matthews]

I'd like to see if we can maintain a single binary that works on 3.6 and
3.7 for ~next month opposed to branching/forking code now.

Thought is, check for capability, if it exists use it, if it doesn't error
out.
For something like the User Impersonation feature of "auto_escalate: False"
we require newer APIs in 3.7, but we can error out if running on 3.6.
This allows the same broker binary to continue to work on 3.6 for next
month while 3.7 issues are being flushed out.



On Tue, Sep 12, 2017 at 9:40 AM, Shawn Hurley <shurley at redhat.com> wrote:

> On 09/12/2017 09:36 AM, Ryan Hallisey wrote:> Let me know your thoughts.
> We can discuss more at today's meeting.
> +1
>
> I would think that we should discuss at either stand up or team meeting
> tomorrow.
>
>
> _______________________________________________
> Ansible-service-broker mailing list
> Ansible-service-broker at redhat.com
> https://www.redhat.com/mailman/listinfo/ansible-service-broker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ansible-service-broker/attachments/20170912/f73e5f2f/attachment.htm>