This portal is to open public enhancement requests against IBM Z Software 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.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
To offer a little background, our initial focus for the managed bundles API was focused on developer use cases. By that we mean, a single developer making changes to e.g. a Java application, wanting to quickly round-trip on changes to that application, and be able to quickly re-deploy it to their target development environment. In particular we wanted to focus on being able to drive that via Maven and Gradle, which we'd anticipate that Java developer to already be using. We did bear in mind there might be other use-cases around deploying to multiple regions (e.g. there's some kind of dynamic routing at play and developers can't tell where the application might get invoked), so it's great to hear more feedback from you in this area. We did consider multiple region deployment when we designed and implemented this feature, but we chose to focus on the developer use-case of deploying to single regions, rather than using the API to migrate bundles between environments.
At the moment we don't have immediate plans to crack open the hood of the managed bundles API, so we're going to decline this request, but we'll certainly bear your feedback in mind, and we'll update you via this idea in the future if we're thinking about changes in this area.