Possible for Forge remote to set baseUrl dynamically?

Forge Forge Platform and Tools
,
1

Is it possible to set the baseUrl on runtime instead of hardcoding in the manifest file.

remotes:
  - key: remote-app-node
    baseUrl: {{derive from app input}}

The reason is to leverage the extended capability of RDS (eg. join and complex aggregation functions). The benefit is… from a data privacy perspective, the user doesn’t have to worry about their sensitive data being processed outside of their environment.

2

Environment variables were released about 1-2 months ago, and I haven’t had a chance to test them yet.
https://developer.atlassian.com/platform/forge/manifest-reference/environment/#environment

app:
  id: "ari:cloud:ecosystem::app/${APP_ID}"
environment:
  variables:
    - APP_ID
3

Thanks, @AndreiPisklenov for sharing the docs. I wasn’t aware of this change.

Anyway, the environment variable approach doesn’t seem to address the problem I am facing. My plan was to allow the user to input some value from the app UI. And apply the value to update the manifest file. (In this case, I want to update the Forge Remote’s baseUrl to point to the customer infra instead of mine).

Seems like a big ask. Still, trying to gauge the feasibility of apps we can build.

4

Hi @PakWaiChoong,

Thanks for reaching out, and explaining your use case.

Unfortunately, at this stage the the baseURL can only be hardcoded in the manifest.

We don’t have an plans at the moment to change this, however, I’ll capture your use case to understand the need if we were to change this in the future.

Cheers,
Daniel.

2 Likes
5

Alright, thanks for the response @DanielReed. Appreciate it