Skip to content

Conversation

@durera
Copy link
Contributor

@durera durera commented Nov 28, 2025

Description

Removes the appconnect role, there has been no development or testing of this role for a very long time; it was removed from our install pipeline due to setting up an insecure integration with MAS and has never been restored. It is being removed as part of the efforts to trim away the unmaintained fat in this collection.


⚠️ Notes for Reviewers

  • Ensure you have understood the PR guidelines in the Playbook before proceeding with a review.
  • Ensure all sections in the PR template are appropriately completed.

@durera durera requested a review from a team as a code owner November 28, 2025 16:32
@durera durera changed the title [major] Remove unsupported appconnect role [major] Remove unmaintained appconnect role Nov 28, 2025
@durera durera merged commit ea71466 into master Nov 28, 2025
2 checks passed
@durera durera deleted the removeappconnect branch November 28, 2025 16:33
@stevealee0
Copy link

AppConnect is needed for Integration flows between IBM ALM applications like MREF to Manage or Envizi to Manage - do we know if this will be supported to install with the CLI at some point again OR or there documents to do this manually from now on?

@durera
Copy link
Contributor Author

durera commented Nov 28, 2025

AppConnect is needed for Integration flows between IBM ALM applications like MREF to Manage or Envizi to Manage - do we know if this will be supported to install with the CLI at some point again OR or there documents to do this manually from now on?

There's no current plans around doing anythign with AppConnect. That can change in an instant, but we haven't even updated the version of AppConnect in our operator catalog since April 2023:

I don't remember the details anymore, but it boiled down to there being no supported way to securely configure AppConnect as part of an automated install due to limitations with the AppConnect product itself; as a result we removed the integration from our install pipelines to prevent customers unintentionally exposing their systems, and there has not been any business reason to revisit AppConnect support in our install in all the time since.

@stevealee0
Copy link

Makes sense and I think this is something our AppConnect product team should be looking at mainly because in the MAS catalogue our listed Add-Ons include the connectors that describe the use of AppConnect as the solution - however custom integration could be used if needed to integrate these solutions and if that were the case then the customer is fully responsible for the security of the integration design/flow so the same applies for AppConnect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants