manageiq-api
manageiq-api copied to clipboard
[RFE] Ability to change Catalog Item Request Info via API
Hi, is there a way how to set or reset VM for a catalog item using rails or API? I can do it in GUI on the following tab:
but I need to do it in a script. I cannot find any relation between a Catalog Item and the data in Request Info. How can I retrieve them and change them if needed?
Thank you very much!
It's possible that's not exposed via the API, as those provisioning forms are some of the oldest in the app (from before we even had an API). I'm going to transfer this to the API repo and mark as an enhancement request.
@kbrock Do you know if we have this?
We have a spec around using the API to update a request. I'm assuming you are talking about the request rather than the contents of the catalog item.
Knowing the actual fields to set here would be tricky, but it looks like it is possible.
https://github.com/ManageIQ/manageiq-api/blob/master/spec/requests/requests_spec.rb#L354-L369
Now that we know we have the endpoint. Is this endpoint good enough? Or do we have some changes we need?
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master
, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
This issue has been automatically closed because it has not been updated for at least 3 months.
Feel free to reopen this issue if this issue is still valid.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master
, please reply with all of the information you have about it in order to keep the issue open.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master
, please reply with all of the information you have about it in order to keep the issue open.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master
, please reply with all of the information you have about it in order to keep the issue open.