On Wed, May 25, 2016 at 4:14 PM, Andrew Wilkins
wrote:
> On Wed, May 25, 2016 at 1:43 PM David Cheney
> wrote:
>>
>> Hello,
>>
>> Several times over this week there has been a call to do X to bring an
>> issue to the tech board's attention.
>>
>> Sadly X has generally be "email", which in my mind
On Wed, May 25, 2016 at 1:43 PM David Cheney
wrote:
> Hello,
>
> Several times over this week there has been a call to do X to bring an
> issue to the tech board's attention.
>
> Sadly X has generally be "email", which in my mind is a shitty way of
> tabling issues for discussion.
>
> - Is there
Hello,
Several times over this week there has been a call to do X to bring an
issue to the tech board's attention.
Sadly X has generally be "email", which in my mind is a shitty way of
tabling issues for discussion.
- Is there an agenda for the tech board?
- Is there a way to add items for the t
I can understand list-clouds vs show-cloud, for plural vs singular (even
though I don't think we actually have commands like that, with a plural and
a singular). But show-config vs get-config seems really pedantic. You're
still showing one thing. One is a foo, one is a foo-config. They have very
e
On 25/05/16 00:12, Marco Ceppi wrote:
Even if you don't expect people to run them, hidding them seems awkward.
Better to simply educate with good help output about what the command
does and when/why use the command.
Was thinking, perhaps it would be better to have a feature flag to use
the "hi
On 25/05/16 01:49, Nate Finch wrote:
While we're on the subject... we have list-foos, show-foos, and
get-foo... and I honestly cannot remember when to use which. Can we just
standardize on one, so no one has to remember if it's list-models or
show-models or show-model-config or get-model-config?
If there are things we really don't want uses to run, they should probably
just not exist in production builds. If they're just less-used commands,
then I don't think it's a big deal to have them in juju help commands.
If we want to remove them from production builds, they could either be
compiled
On Tue, May 24, 2016, 12:19 AM Tim Penhey wrote:
> Hi folks,
>
> More from the "let's fix the output" school of thought.
>
> One thing that has bugged me about 'juju help commands' was the repeated
> mentions of "alias for ".
>
> I propose that we don't show aliases by default, and allow the user
Hidden would be a primitive defined in the github.com/juju/cmd package,
whereas the "blockable" consideration is an implementation detail of
juju commands.
I don't think we should specify them the same way.
However, that doesn't mean that Juju shouldn't have a base blockable
command which the
