IBM Cloud - Structured Ideas
This portal is to open public enhancement requests against IBM Cloud and its 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.
IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.
Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
I believe this request is related to "Classic" delivery pipeline. In Tekton pipelines changes to the pipeline happen in code, in a repo, so there is an audit trail. The few cases in Tekton where this is not true will be moving in that direction. There is no plan to address this in Classic pipelines.
Execution logs can be persisted from the pipeline, see the DevSecOps reference implementation templates for an example of preserving evidence in a repo.
If I'm missing some other aspect of this request please let me know.
This is a nice feature to have! Especially when we deal with production pipelines with complicated configurations. This feature could help the team easily debug what went wrong and what should be done if there is anything wrong with the pipeline.
This would be great as we had issues where changes to the pipeline occured but we had no record of what or how it happened. There should be a place where you can see the logs of any issues or modifications made to the pipeline