This repository has been archived by the owner on Jul 26, 2023. It is now read-only.
Incorporate the MIQ API Client Python library as the core to the CLI calls #23
Comments
ryankwilliams
added a commit
that referenced
this issue
Jan 22, 2018
Previously the client_api decorator would set the collection api pointer
attribute to easily access the client api library when the method is
run. This still would require code to lookup the exact collection
object from the api pointer and that collection pointer action to be
run. This commit provides three new attributes:
1. collection: the exact collection reference.
-> i.e. provider collection class `collection` attribute has the ref
to the provider collection only.
2. all: all entities regarding the collection.
-> i.e. provider collection class `all` attribute has all the
entities regarding the provider collection.
3. action: the exact collection action reference.
-> i.e. provider collection class `action` attribute has the ref
to the provider action only.
This change will be used by #23
|
This library has been incorporated to the core of the CLI. Every collection has access to the client API to perform requests in the given collection. Closing this issue due to previous PR's resolve this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to leverage the following project [1] to be used as the core underlying component to the CLI. This library provides access to MIQ REST API collections via Python. Our collections modules can use this library to perform the actions interfacing with MIQ.
This issue is to implement the solution on how we can incorporate this library into all collections. Maybe it is included as a mixin class to all collections classes, a utility module, etc.
[1] https://github.com/ManageIQ/manageiq-api-client-python
The text was updated successfully, but these errors were encountered: