<div dir="ltr"><div>Would the broker-client-go be essentially a vendorable dependency  like the client-go package in kubernetes? Do I understand that correctly? At a high level, what would be in the broker-client-go?<br><br></div>-Ryan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 20, 2018 at 1:43 PM, <a href="mailto:cbrookes@redhat.com">cbrookes@redhat.com</a> <span dir="ltr"><<a href="mailto:cbrookes@redhat.com" target="_blank">cbrookes@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">I think that is a great way of doing it! We use the generators for our mobile crd types and it is working well for us. I would really like if the service catalog had taken the approach of a separate repo for the client maybe we could suggest it?<br><br><div id="m_8482382357315667036AppleMailSignature">Craig</div><div><div class="h5"><div><br>On 20 Feb 2018, at 18:33, Shawn Hurley <<a href="mailto:shurley@redhat.com" target="_blank">shurley@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div>Hello All,<div><br></div><div>I wanted to send out a note to make sure that everyone was ok with the approach for the k8s like client for broker CRDs.</div><div><br></div><div>I was thinking that we would create a new repo, I assume we need a new org (automationbroker or something similar), and this would contain the broker-client-go.</div><div><br></div><div>The client would be generated using the k8s generate client scripts and code. Here is a blog post about how this works for some context: <a href="https://blog.openshift.com/kubernetes-deep-dive-code-generation-customresources/" target="_blank">https://blog.<wbr>openshift.com/kubernetes-deep-<wbr>dive-code-generation-<wbr>customresources/</a></div><div><br></div><div>This client then would be added to the broker through glide/dep. </div><div><br></div><div>If the above is agreeable some help/guidence on next steps for making the new repo would be appreciated.</div><div><br></div><div>Thanks,</div><div><br></div><div>Shawn Hurley</div><div><br></div></div></blockquote></div></div><blockquote type="cite"><div><span>______________________________<wbr>_________________</span><br><span>Ansible-service-broker mailing list</span><br><span><a href="mailto:Ansible-service-broker@redhat.com" target="_blank">Ansible-service-broker@redhat.<wbr>com</a></span><br><span><a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/ansible-<wbr>service-broker</a></span><br></div></blockquote></div><br>______________________________<wbr>_________________<br>
Ansible-service-broker mailing list<br>
<a href="mailto:Ansible-service-broker@redhat.com">Ansible-service-broker@redhat.<wbr>com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/ansible-service-broker" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/ansible-<wbr>service-broker</a><br>
<br></blockquote></div><br></div>