now that hammer is using dynamic bindings, do we need to continue to use/update foreman_api and katello_api? or can those be EOL'd?
thanks
···
-- Adam Price Software Engineer Red Hat Inc., Raleighadprice at redhat dot com
now that hammer is using dynamic bindings, do we need to continue to use/update foreman_api and katello_api? or can those be EOL'd?
thanks
adprice at redhat dot com
We can drop them from the cli's perspective. What other components do
use it? Installer?
–
Dominic Cleal
Red Hat Engineering
> >> now that hammer is using dynamic bindings, do we need to continue to
> >> use/update foreman_api and katello_api? or can those be EOL'd?
> >>
> >> thanks
> >>
> >
> > We can drop them from the cli's perspective. What other components do
> > use it? Installer?
>
> Yes,
> https://github.com/theforeman/puppet-foreman/blob/master/lib/puppet/provider/foreman_smartproxy/rest.rb.
alright cool, so we'll keep building foreman_api. if nobody speaks up about katello_api, i'm going to pull it from nightly builds tomorrow morning.
thanks all!
–
Dominic Cleal
Red Hat Engineering–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Just for the record, staypuft installer script (hopefully foreman provisioning
setup part of foreman-installer in future) use foreman_api. So +1 for keeping
it.
On Monday 24 of March 2014 11:53:47 Adam Price wrote:
----- Original Message -----
On 24/03/14 09:38, Tomas Strachota wrote:
On 03/20/2014 08:34 PM, Adam Price wrote:
now that hammer is using dynamic bindings, do we need to continue to
use/update foreman_api and katello_api? or can those be EOL’d?thanks
We can drop them from the cli’s perspective. What other components do
use it? Installer?Yes,
https://github.com/theforeman/puppet-foreman/blob/master/lib/puppet/provid
er/foreman_smartproxy/rest.rb.
alright cool, so we’ll keep building foreman_api. if nobody speaks up about
katello_api, i’m going to pull it from nightly builds tomorrow morning.thanks all!
–
Dominic Cleal
Red Hat Engineering–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm aware of many users using it, please keep it.
Ohad
Just for the record, staypuft installer script (hopefully foreman
provisioning
setup part of foreman-installer in future) use foreman_api. So +1 for
keeping
it.