Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Status Future consideration
Workspace App Connect
Created by Guest
Created on Apr 10, 2024

Disable warning message of ACE ephemeral storage if it has been configured intentionally

Currently the CP4I integration instances overview at URL/instances shows the warning message "Ephemeral storage has been selected for this instance, this is not a resilient storage mechanism, if the pods are restarted all contents will be lost which may affect any IntegrationServers configured with associated BAR files." for the ACE dashboard even though the configuration has been done intentionally.

I would prefer to have an additional configuration option to disable this warning message when the configuration of ephemeral storage has been done intentionally.

Idea priority Low
  • Admin
    Ben Thompson
    Reply
    |
    May 7, 2024

    Idea Review. Thank you for taking the time to raise this enhancement request. We agree that this is a good suggestion for enhancing usability, as a user could get irritated by seeing this warning. Providing an additional configuration option within the ACE operator would provide a technical means to suppressing the warning message in the chosen circumstances.

  • Guest
    Reply
    |
    Apr 19, 2024

    HI App Connect - could you consider this one please? Happy to chat about the use case if you need to.

  • Guest
    Reply
    |
    Apr 19, 2024

    Hi Jan,

    Thanks for coming back on this one. From our chat it looks like your use case is:

    "When I create an App Connect Dashboard, I'm storing my BAR files elsewhere (Or building images with them in) therefore I don't want/need the BAR store functionalilty and the associated storage. Coud 'provision the BAR store (with storage) be made optional?"

    Passing this to the App Connect team for appropriate consideration. (I've changed the status back to 'Submitted' so that it shows up in their feed at the correct place)

    1 reply
  • Guest
    Reply
    |
    Apr 11, 2024

    Hi Andy,

    Thanks a lot reaching out to me!

    1. Until now I only saw such a warning message as of the configuration for ephemeral storage or therefore I would be good to be only able to configure those. Anyhow you will know better whether there could be more warnings emitted by intented configuration changes.

    2. If this warning status is displayed within CP4I platform navigator and additionally even reported to kubernetes, I prefer to disable both functionalities at the same time.

    Kind regards
    Jan

  • Guest
    Reply
    |
    Apr 11, 2024

    Thanks for raising this - a couple of questions:

    1. Is this purely around the warnings for ephemeral storage - or does it apply to any other warnings in particular?
    2. Is this relevant just in the CP4I platform navigator - or is it needed in the statuses reported to kubernetes by the Custom Resource itself?

    1 reply
  • Guest
    Reply
    |
    Apr 10, 2024

    Implementing the option to disable the warning message for intentional configurations of ephemeral storage in ACE is a valuable addition for several reasons:

    1. User Control: It empowers users by giving them control over their environment. Users who are aware of the implications of using ephemeral storage and have chosen it deliberately should have the option to suppress warnings that are not relevant to their use case.

    2. Clarity: The warning message is intended to alert users of potential risks, but when the configuration is intentional, the message can become noise that clutters the interface. Disabling it can lead to a cleaner, more focused user experience.

    3. Efficiency: For experienced users, constantly dismissing or ignoring this warning can be a nuisance and a waste of time. The ability to disable the warning can streamline their workflow, allowing them to focus on more critical tasks.

    4. Customization: It aligns with the principle of customizable user interfaces, where users can tailor the system to meet their specific needs and preferences, enhancing overall satisfaction with the product.

    5. Best Practices: It encourages users to make informed decisions about their configurations. By providing the option to disable the warning, it implicitly prompts users to learn more about ephemeral storage and assess whether it is the right choice for their scenario.

    Overall, this feature would enhance the user experience for those who have a clear understanding of their storage needs and have intentionally chosen ephemeral storage for its benefits. It's a step towards a more personalized and efficient integration environment.

  • Guest
    Reply
    |
    Apr 10, 2024
    This is actually a great idea! Since those warning messages sometimes can be interpreted as an error by our monitoring system.