[Pulp-dev] writing a new crane search provider for container images

[Tom McKay]

Thanks! It occurred to me this morning that without 'docker login' mapping
to foreman users this would be largely an intellectual exercise. So... what
are my choices for auth support?

On Tue, May 30, 2017 at 10:39 AM, Michael Hrivnak <mhrivnak at redhat.com>
wrote:

> It's relatively simple from the crane side. You just need to make a
> subclass of SearchBackend:
>
> https://github.com/pulp/crane/blob/python-crane-2.1.0-1/cran
> e/search/base.py#L14
>
> And  probably you'll want to use the HTTPBackend found below it. It's
> mostly just a matter of figuring out how to pass a search query to forman,
> and how to convert whatever results it gives you into SearchResult
> instances. Focus on just implementing your own search() method that does
> this, and use the other methods if/when they are useful.
>
> The two examples, for Solr and Google Search Appliance, are good examples
> of how it should work.
>
>
> On Mon, May 29, 2017 at 9:42 PM, Tom McKay <thomasmckay at redhat.com> wrote:
>
>> Some months back I set up a solr search provider for crane[1]. I set up a
>> repeating task in foreman[2] to populate solr with the latest repository
>> information. As I was doing this, though, it seemed that it would make more
>> sense to have crane query foreman directly for the information. Is there
>> anyone familiar with search integration with crane that could guide me in
>> setting up foreman as a provider?
>>
>>
>> [1] http://docs.pulpproject.org/en/nightly/plugins/crane/index.
>> html?highlight=crane#solr
>> [2] https://theforeman.org/plugins/katello/
>>
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>>
>
>
> --
>
> Michael Hrivnak
>
> Principal Software Engineer, RHCE
>
> Red Hat
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170530/64195cb1/attachment.htm>