RFC-94: Configurable Egress and Remotes

Hi everyone,

A big thank you for your feedback on the RFC - it’s helped validate that we’re heading in the right direction, but has also supported some introspection of the capability and mechanisms to improve it. Covering some key feedback and questions below to close this out.

Runs on Atlassian support
We appreciate the feedback related to Runs on Atlassian and understand the motivation which a lot of apps have to achieve this. As @JamesDumay noted in this post, we are performing further exploration of how customer would perceive a capability such as configurable egress within Runs on Atlassian.

Major / Minor Updates
We’ve further explored scenarios where updates would need to / not need to occur. Similar to recent work with bulk-upgrade and the inheritance of Connect scopes, we’re striving to apply a principle of privilege escalation leading this. For example, if adding configurable egress would be a minor update, as the admin would later approve the elevation of permissions in the modal. Similarly, if a remote is changed to configurable and retained its existing remote as the default, that too would be minor.

For those wanting to follow our delivery of this, we have added it to the Forge Roadmap and will continue to provide updates here.