Bug #6569 api smart-proxies does not return lifecycle environments

http://projects.theforeman.org/issues/6569

Trying to figure out how best to represent a smart proxy in json when returned in foretello.

First, there can be only a single smart proxy object with a given url; it must be shared across all orgs that wish to use it. It is resources like this that are going to really be troublesome when running foreman+katello since users in every org it appears in will wish to perhaps have edit permissions. Perhaps not a problem but something to be aware of.

Specifically when in foretello, though, there is another aspect: Katello extends the smart proxy model to include references to lifecycle environments, hosts, and hostgroups. However, since SP spans orgs, this will be a jumble of references that span those same orgs. What should the json for a SP look like?

As a side note, editing a SP in the UI in org A properly displays just A's lifecycle environments for inclusion. However, switching to B and modifying the SP w/ B's lifecycle environments effectively erases any that were previously associated from A. (I believe there may be an already existing catch-all bug for this since the same behavior exists (existed?) when edit relationships on the org page itself. (ie. If the user did not have permissions to see all templates, when they saved their choices it would erase any previous assocations.)

··· -- @thomasmckay


“The leader must aim high, see big, judge widely, thus setting himself apart form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle

“Leadership is about making others better as a result of your presence and making sure that impact lasts in your absence.” ~ Harvard Business School

> Bug #6569: api smart-proxies does not return lifecycle environments - Katello - Foreman
>
> Trying to figure out how best to represent a smart proxy in json when returned in foretello.
>
> First, there can be only a single smart proxy object with a given url; it must be shared across all orgs that wish to use it. It is resources like this that are going to really be troublesome when running foreman+katello since users in every org it appears in will wish to perhaps have edit permissions. Perhaps not a problem but something to be aware of.

I think this is okay and desired, as smart proxies are infrastructure
and it would be expected to share these across orgs. You should be able
to set one up solely for a single organization though.

>
> Specifically when in foretello, though, there is another aspect: Katello extends the smart proxy model to include references to lifecycle environments, hosts, and hostgroups. However, since SP spans orgs, this will be a jumble of references that span those same orgs. What should the json for a SP look like?
>
> As a side note, editing a SP in the UI in org A properly displays just A's lifecycle environments for inclusion. However, switching to B and modifying the SP w/ B's lifecycle environments effectively erases any that were previously associated from A.
This page is completely separate from the orgs/locations pages. Can you
file an issue for it specifically?

Thanks!

··· On 07/10/2014 04:03 PM, Tom McKay wrote:

(I believe there may be an already existing catch-all bug for this since the same behavior exists (existed?) when edit relationships on the org page itself. (ie. If the user did not have permissions to see all templates, when they saved their choices it would erase any previous assocations.)