Cloud Platform
This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you very much. We will share this with the development team and be in touch soon.
Ultimately both, but happy if two separate APIs.
We have an automated process that triggers a new version creation and currently checks to see if the version name we are expecting has created, but due to the time it can potentially take we have a polling process that checks every 5 mins for 30 mins. Sometimes the version creation fails after 1-2 mins, but as we can't check if there is an active running job or the historical runs to check for a failure, we have to wait 30 mins for the process to fail.
As a minimum. if we can check for active jobs we can then check to see if our version has been created, but it would also be useful to be able to check the history for failed jobs to identify what the issues were too.
To help our development team properly design the solution for you, can you please share with us the use case or what you intend to do with the results? This will help us design the CLI that we would add for you.
Is your end goal to see this in historical runs or the current running jobs?
We have created a discussion topic and will be meeting with the development team to review this request. Thank you and we will be in touch with updates.
Thank you for submitting this idea. We will be reviewing this shortly with our team.