This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
I do not understand the rationale for the current behavior. The web client allows users to un-archive streams and baselines. We are asking for this behavior via REST also.
If it's considered as "not existing at all and with no distinctions from configurations that never existed", then why is it part of the response from a GET request to https://<server>:9443/rm/cm/component/<component_uri>/configurations?
It would be useful when sending a GET request for all configuration (streams and baselines) of a component. For example, if I loop through the configurations provided by the following uri, I will get an HTTP 404 error when sending a get request for any archived configuration:
https://<server>:9443/rm/cm/component/<component_uri>/configurations
The only ways to capture that it is archived is to do error handling, but it would be better to be able to get a response that notes that it is archived through an attribute, or even to remove the archived configuration from the configurations provided from the above uri. Others might want to get details from an archived configuration.