notableaddedAtlassian calls it: Added
Dynamic modules, customer-managed egress, and customer-managed remotes are now generally available in Forge
- Announced
- Tags
- forge-core-platform, forge-jira-cloud-platform, forge-jsm-cloud, forge-confluence-cloud
- Severity
- notable, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3512
Dynamic modules, customer-managed egress, and customer-managed remotes are now generally available on the Forge platform.
- Dynamic modules let a Forge app register and manage modules at runtime through the Dynamic Modules API, rather than declaring them statically in the manifest. These modules are available across Jira, Confluence, and Jira Service Management.
- Customer-managed egress lets Atlassian administrators configure the external domains a Forge app may send data to.
- Customer-managed remotes let Atlassian administrators configure the remote backends a Forge app may communicate with.
For more information, see Dynamic modules and Customer-managed egress and remotes.
More details
These capabilities are not currently supported for Atlassian Government Cloud.
These capabilities follow their earlier Preview releases: Forge Dynamic Modules Preview and Customer-managed egress and remotes Preview.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.