<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 23, 2020 at 3:31 PM Robin Chan <<a href="mailto:rchan@redhat.com" target="_blank">rchan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-family:RedHatText,sans-serif">
Robin Chan<span style="color:rgb(170,170,170);margin:0px;font-size:14px"></span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;text-transform:capitalize;font-family:RedHatText,sans-serif">She/Her/Hers</p>
<p style="font-weight:normal;margin:0px;font-family:RedHatText,sans-serif">
<span>Satellite Software Engineering Manager - Pulp</span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;font-family:RedHatText,sans-serif">
<a style="color:rgb(0,136,206);margin:0px;text-decoration:none;font-family:RedHatText,sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span></span></a>
</p>
<div style="margin-bottom:4px">
</div>
<p style="font-weight:normal;margin:0px;font-family:RedHatText,sans-serif">
IRC: rchan
</p><p style="margin:0px;font-family:RedHatText,sans-serif"><span style="color:rgb(0,0,0);font-family:Overpass,"Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif">Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.</span><span style="font-weight:normal;font-size:12px"><span><br></span></span></p>
<div style="margin-top:12px">
<table border="0">
<tbody><tr>
<td width="100px"><a href="https://www.redhat.com" target="_blank"> <img src="https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png" width="90" height="auto"></a> </td>
</tr>
</tbody></table>
</div>
</div><div><br></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 23, 2020 at 12:45 PM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">## Sept 23, 2020<br><br>* [david] Finish CLI PoC demo and upload to asciinema<br>* Send out email to pulp-list about PoC?<br> * Include asciinema<br> * How to install, use CLI<br> * Ask for feedback<br> * Contact mcorr first and see what she recommends<br>* Should we meet regularly?<br> * Meet again in two weeks<br> * Hopefully have some user feedback<br>* We need a decision about where to have the cli code<br> * it's not urgent.<br> * for now, keep using a single repo<br></div></blockquote><div>I was hoping someone would chime in here on what would be the cli experience of a plugin that isn't in the pulp org - say debian or chef?</div><div>What would be simplest? Or is there an option that would be hard to change back the other way? This seems like a pretty important decision. I'd like to see some use cases or requirements that might help determine a decision or rule out any. And I'd like to hear from other stakeholders.</div></div></div></blockquote><div>I agree simplicity is key. Here are some questions/thoughts I have to try to determine what simple looks like<br></div><div><br></div><div>One question I have is: will plugins have custom commands. I suspect the answer is yes because even if the CLI package itself is smart enough to auto-produce all the generic commands from the API spec, I suspect in most cases plugins will want "custom commands".</div><div><br></div><div>So if that's a yes, how will they ship those? While it's simple to add them to the one CLI repo, it's complicated for users to get the "right" version for them when it's all in one package. In fact that may be impossible. So not as simple, but likely more usable would be for any custom CLI commands to ship as a "CLI plugin package" aka a python package that will give extra commands and have this auto-release when the plugin itself releases. What wouldn't be simple is an additional repo for each plugin that would require additional complexity at each plugin release.</div><div><br></div><div>The final question I wonder about is testing: How will CI be done on these commands? My take is probably simplistic, but CI it anywhere plugin bits are released from so if that's one main repo for the CLI CI those parts there, and then CI any custom commands from repos where they are released from.</div><div><br></div><div>This is what I was thinking about, but I am ok with anything the CLI teams would be better or simpler.<br></div><div><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">* Supporting multiple versions of pulpcore and plugins<br> * For now, use conditional statements when needed<br>* Versioning of the CLI<br> * Needs more thought<br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>David</div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div></div>