Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management and AIOps 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 Fabio for taking the time to provide your ideas to IBM. We value the relationship with you and appreciate your willingness to share details about your ideas. IBM has evaluated the request and has determined that it cannot be implemented at this time or does not align with our current strategy or roadmap. If you have any additional feedback, thoughts or ideas, or if there is anything else we can do, please do not hesitate to reply to this message to continue the conversation. As Eva mentioned we are looking at a framework approach/path to send our actions into any GitOps pipeline. Thanks
Webhooks are unfortunately not designed to be VCS (Version Control Software aka the Source of Truth) clients to allow for merge / commit actions.
Turbo actions are always available via API and webhooks can take actions to another place. But then another program would need to convert the actions and merge that into the VCS source of truth. Webhooks would not be able to handle the challenge of merging into Helm charts and values.yamls, which requires a map or translator of how limits/requests are exposed and specified.
Kubeturbo discovering repo, branch etc is not a given either because people can implement pipelines to have a hub cluster server (ArgoCD has such a hub configuration), which means that we need another mechanism to feed into the framework workload path, repo, relevant VCS info.
Turbo is looking at other frameworks such as Kubestellar, and even partnering with another company who has the ability to send our actions into any GitOps pipeline.