Hi,
Thanks for opening up this discussion. I've opened a feature request here
[1] for all to track. We'll be looking into ways to make the store more
informative especially for charmers and users in the following weeks, so if
you have any other ideas that you'd like us to consider, we'd love to
To go back to the original request from Ondřej and Merlijn, I would also
like to see something a bit more queryable than just
http://interfaces.juju.solutions/
Can we put in a bug/request somewhere so it can be tracked?
--
Sandor Zeestraten
On Tue, Oct 25, 2016 at 11:26 PM, Marco Ceppi
It sounds like you really want to add landscape client to each ;)
On Tue, Oct 25, 2016, 10:21 PM Casey Marshall
wrote:
> On Mon, Oct 24, 2016 at 6:15 AM, Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
> +1 for "which charms use this layer" queries.
On Mon, Oct 24, 2016 at 6:15 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> +1 for "which charms use this layer" queries. This has a number of uses:
>
> - for finding what the quality of a layer is (more use in recommended
> charms = better quality)
> - for the maintainer of a
Seems like a good idea, but can't help you here, sorry.
2016-10-24 15:26 GMT+02:00 Charles Butler :
>
> > - to see which charms have to be rebuilt if a vulnerability has been
> found in a layer
>
> There was a fair amount of talk about static and dynamic code
> - to see which charms have to be rebuilt if a vulnerability has been
found in a layer
There was a fair amount of talk about static and dynamic code analysis at
DevOps Days KC.
If I ever come up with free time again I'd love to take a look at what that
looks like for us in terms of charm code.
Hi,
developing new charms or just exploring the store, one might want to
raise random queries like "which charms use a layer x", "which charms
are subordinate" and some others. Are there any plans to add those,
concerns why this might not be a good idea?
While the store could extend the API to