Forge Remote Multiple Environments

Forge Forge Platform and Tools
,
1

Hello,

I would like to use the forge remote app but at this time there seems there isn´t a way of having different endpoints depending on each environment I deploy my app. E.g. If I deploy my forge app to a developement environment I would like to use my development remote and so on.

The only way I can now do this is by having environment variables as mentioned here to replace the urls:
https://developer.atlassian.com/platform/forge/manifest-reference/environment/

Is there a better way of doing this?

Also would be cool if I could change the endpoint at runtime.

Thanks

1 Like
2

Hey @jonymilk,

Environments variables are the best mechanism to achieve this today, however remotes are statically declared in the manifest at deployment, which you’ve noted. We’re tracking the ability for users to dynamically declare a remote URL under [FRGE-1227] - Jira - I’d recommend voting on this ticket and leaving a comment if it’s applicable to your use case.

3 Likes
3

Hi Sean,
FRGE-1227 doesn’t really align with this behaviour (at least, not for us).
Having a Remote defined on a per-environment basis would be the end goal. However, as you have mentioned, only 1 static URL can be provided, shared across all environments.

Including this configuration in the request context and proxying the request has already lost the ability of defining per-environment Remotes. Following from this, the app Remote compute is telling customers that data will be processed/fetched from the static defined Remote. In this case, can you confirm if it is permitted to compute data outside of this Remote? (My guess is no, because that’s the whole reason the customer is being made aware of the egress, and if not, how are developers supposed to handle per-environment Remotes?).

FRGE-1227 isn’t viable or sufficient for this. Redeploying the app with a new remote will update all environments.

Update: Oh, and RFC-94 is also not helpful, as the configurable egress has already defined the remote in the manifest.

4

Hey @DennyMiller,

Could you please expand on what you mean regarding a remote per-environment - does this relate to the development of your site (i.e. development, staging, production), or customer installations?