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).
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.
email@example.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
First part of article was published and covers what to do with the archive files:
A Blog/Article/Technote/Whitepaper will be created (in the next few weeks) to describe how to handle archived artifact versions.
Thank You for your input.
I will check with development.
Any update on the technote? We are still waiting for it and the status has changed to Not under consideration.
Also, as I mentioned "I believe IBM doesn't recommend touching the file system from the backend. Is this something officially documented somewhere? If not, I would recommend to please consider this again or provide an alternate solution that helps us resolve this problem with no issues from vendor support side."
The clients are facing issues with storage management with UCD codestation. I am not to able to understand how implementing this within the ucd would not bring any more value to the tool? We are looking for a permanent solution for this within the tool itself and do not want to touch the file system from the backend. Please advise.
Yes, it helps. Please update when the technote is available.
We will work on a solution, first short term with providing a technote/article how to proceed with archived files. And long term we need to rethink how we will handle archiving.
Does this information helps you?
I believe IBM doesn't recommend touching the file system from the backend. Is this something officially documented somewhere? If not, I would recommend to please consider this again or provide an alternate solution that helps us resolve this problem with no issues from vendor support side.
I would also like to mention the behavior of artifacts as it was confirmed in a support case. If an archived file is retrieved back (unarchived) to codestation the zip of that file still stays in the archived location. If you look at this scenario - the version is now unarchived but an archived version of it is still present in archive location. How can we skip such versions when deleting the old files manually from the archive for e.g., using the timestamp? or, is it ok to delete them and it will get archived again with a new timestamp from the codestation? Or, what's the behavior when the same version that's already in archive is getting archived again because it was unarchived earlier? it's not clear if it's working as it should or if it's a defect?
It's these types of scenarios that a customer wants to avoid. So, we request IBM as the vendor to provide a stable vendor supported solution for deleting archives.
Thank You for your RFE/IDEA. It is always possible to remove unneeded files from the archive location using external solutions (backup-tools, scripts, manual intervention). Adding such a functionality to UCD would replicate this kind of functionality and would not bring additional value to it.
Please consider using external tools build for this kind of feature set.