Complex store queries

Merlijn Sebrechts merlijn.sebrechts at gmail.com
Tue Oct 25 08:50:41 UTC 2016


Seems like a good idea, but can't help you here, sorry.

2016-10-24 15:26 GMT+02:00 Charles Butler <charles.butler at canonical.com>:

>
> > - 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.
>
> Something like OWASP <https://www.owasp.org/index.php/Main_Page> but not
> limited to just webapps.
>
>
> Would you happen to have any information around this subject Merlijin?
>
>
>
> Charles Butler <charles.butler at canonical.com> - Juju Charmer
> Come see the future of modeling your datacenter: http://jujucharms.com
>
> On Mon, Oct 24, 2016 at 6:15 AM, Merlijn Sebrechts <
> merlijn.sebrechts at 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 layer so he can see what the impact is of a
>> change on his layer
>> - to see which charms have to be rebuilt if a vulnerability has been
>> found in a layer
>>
>> 2016-10-18 16:55 GMT+02:00 Ondřej Kuzník <ondrej.kuznik at credativ.co.uk>:
>>
>>> 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 include these, I presume it
>>> would just be an addition to a hardcoded list. Another option would be
>>> for someone to scrape the store to PostgreSQL or a document DB of some
>>> sort that could be searched with rather arbitrary queries (and a few
>>> indexes for the more common ones).
>>>
>>> My first reaction is that such a scraper would be frowned upon as it
>>> might not have a way to update its database intelligently and keep
>>> hitting all sorts of rate limits imposed by the store, but I might be
>>> wrong here.
>>>
>>> Any thoughts on this?
>>>
>>> Thanks,
>>> Ondrej
>>>
>>> --
>>> Consultant
>>>
>>> credativ Ltd
>>> Open Source for Business
>>> UK office:  +44 1788 298150
>>> Email:      ondrej.kuznik at credativ.co.uk
>>> Web:        http://www.credativ.co.uk
>>> Suite 5 | Bloxam Court | Corporation Street | Rugby | CV21 2DU | UK
>>>
>>> We would love to hear your thoughts on our service!
>>> Please send your comments to feedback at credativ.co.uk
>>>
>>> credativ Ltd is registered in England & Wales, company no. 5261743
>>> Certified by CompTIA / AccredITUK with the ICT Supply standard of
>>> quality for Software Product Design and Development
>>>
>>>
>>> --
>>> Juju mailing list
>>> Juju at lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/juju
>>>
>>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161025/ee1deb81/attachment.html>


More information about the Juju mailing list