The duffy linch-pin plugin does not use the Inventory call at all, thus will not be affected by this. However, if we decided to implement a lookup to see if the specific set of nodes by ssid exists would ever be the reason we would use it. And to do so, we would have the api key value already.

herlo

On Thu, Aug 11, 2016 at 4:21 PM, David Moreau Simard <dms@redhat.com> wrote:

In cicoclient the "cico inventory" command will do a call with no API key if none is provided and will do one if an API key is provided.. simple as that.

I can change the command to require an API key so that we can avoid needlessly doing a call that won't work.

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]


On Aug 11, 2016 5:48 PM, "Karanbir Singh" <mail-lists@karan.org> wrote:
hi

We are going to change the way the backend inventory works to
accommodate different architectures, different type of deployments and
different ways to return/teardown CI hosts.

As a result, users will no longer be able to call the /Inventory API
call for a complete state, you will need to supply your apikey for it to
return anything worthwhile.

For existing calls that already supply the apikey ( I believe the cico
client does ), there should be no change. But for anyone doing a generic
blanket call to get entire stock report, they will get an empty result set.

Is this going to impact anything anyone has in production right now ?

Regards,

--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
_______________________________________________
Ci-users mailing list
Ci-users@centos.org
https://lists.centos.org/mailman/listinfo/ci-users

_______________________________________________
Ci-users mailing list
Ci-users@centos.org
https://lists.centos.org/mailman/listinfo/ci-users