Re: Proposal: display-name for charm metadata

On Sat, Sep 24, 2016 at 11:34 AM Alex Kavanagh wrote: > Why not allow the display of the name to be case sensitive, but all usage > to be case insensitive? So name is MySQL, but you can juju deploy mYSqL if > you really wanted to. > I expect display names may also

Re: Proposal: display-name for charm metadata

On Sat, Sep 24, 2016 at 11:34 AM Alex Kavanagh wrote: > Why not allow the display of the name to be case sensitive, but all usage > to be case insensitive? So name is MySQL, but you can juju deploy mYSqL if > you really wanted to. > I expect display names may also

Re: Proposal: display-name for charm metadata

Why not allow the display of the name to be case sensitive, but all usage to be case insensitive? So name is MySQL, but you can juju deploy mYSqL if you really wanted to. On Sat, Sep 24, 2016 at 2:50 PM, Marco Ceppi wrote: > Hey everyone, > > I know we're rocking

Re: Proposal: display-name for charm metadata

Yeah sounds reasonable but I would be wary of over engineering. Tom On 24 Sep 2016 14:59, "José Antonio Rey" wrote: > As long as it's an optional field, I would say this is one worth having. > Makes it easy to follow naming guidelines. > > However, it would be nice for charm

Re: Proposal: display-name for charm metadata

As long as it's an optional field, I would say this is one worth having. Makes it easy to follow naming guidelines. However, it would be nice for charm names to not be case sensitive. That way, one would be able to deploy `juju deploy mysql` or `juju deploy MySQL` without troubles, since when one

Proposal: display-name for charm metadata

Hey everyone, I know we're rocking towards 2.0 but this is a problem I've seen voiced a few times now. To date, the `name` field in charm has always been [a-z-0-9_-] where you can't end with `-#`. This makes sense, simple flat names that are all lowercase make it easy to do `juju deploy