Hi Nick, we’re targeting Q3 2021 (calendar). I’ll need to confirm that the region support in product automatically flows on to apps, but am pretty sure it does, or can follow very soon after.
The current behaviour of Connect is as follows: If an instance is in a given realm, say the EU, and an application supports the EU and the US, it will install into the EU regardless of whether the instance is an Enterprise instance that has data residency enabled.
- Is this also true for our developer instances?
- What happens when uninstalling / reinstalling an app, will it determine the realm as if this was a new app or will it use the realm from the previous installation?
Really interested in an answer to @dbenson 's question as well. Will there be any indicator in the lifecycle call of the realm the app is installed for? Especially when reusing the same url for different realm, like for example for global and US.
@g.j.streek I’ve got an answer from Atlassian about this. The realm is set at instance creation time. This means that if a customer pinned to EU and has your app installed, once your app starts supporting data residency, Jira will still use the previous app URL and nothing will change.
Thanks @VitorPelizza. Any idea on how to test a regional install from a developer instance?
What happens when uninstalling / reinstalling an app, will it determine the realm as if this was a new app or will it use the realm from the previous installation?
When re-installing an app, there is no record of the previous installation, so it will behave as if it was a new installation. It won’t automatically re-use the same installation URL. If the customer’s site is still in the same realm, then it will use the same installation URL.
@g.j.streek unfortunately I didn’t try it myself, but I suppose you’ll need to create a new Cloud instance from scratch so that you can choose a specific realm for it.
Hey @HeyJoe, do you think you guys would be able to summarise the discussions and the current behaviour for app installations in a proper developer’s documentation? I think that’d be super helpful for everyone.
@HeyJoe We now have an instance to test on, with the realm pinned to the EU:
Nontheless the app gets installed in the global realm. Is there any way we can debug this / get help to find out what we are missing?
@g.j.streek I have asked the dev team to investigate.
We have identified the problem and a solution is rolling out now. @SushantBista will be able to provide an update once things are fixed.
Great, thanks. @SushantBista do you have an update? Just retested it and still getting installs from the global realm.
As a follow-up to what was asked above, as a market vendor how do we get a test environment created in a specific realm?
Hi @g.j.streek, the data residency feature flag caused some issues for app installs - and so we have temporarily switched it off. This is the reason as to why your test app is getting assigned to global.
We are currently implementing the fix and planning to roll out to a selected number of test instances first, before doing a complete roll-out. I will update you once fix is in place to retest on your test instances. I apologise for any testing delays this may have caused.
Looking forward to that roll-out and the update!
Hi Everyone, just an update that the data residency feature flag has been fully rolled out.
Please note that this is currently an EAP feature - and does not yet support realm migrations or a full customer experience (which is currently in the works).
Please let me know if you have any issues or questions.
@SushantBista, just to clarify, how do we get a test instance with data residency for apps enabled? We just need to create a new Cloud instance pinned to a region?
Hi @VitorPelizza, yes a new cloud instance can be created. If you have existing test instances (which are already region pinned), these can also be used. After updating your app descriptor with the relevant regionBaseUrls, any subsequent app installs for a particular site go to the site region preference. If the region that the instance is pinned is not declared in the app descriptor, the app data will just go to the the default region outlined in the descriptor.
Is there any information on if/when the Atlassian Connect Express library will support this.
I can see the alternate regions URLs can be added into the descriptor with ACE, but currently I believe ACE always returns (global) localBaseUrl to users so even if the pinned instance initially connects to the regional stack, ACE will generate links/redirects to localBaseUrl?
Hi @Chris_at_DigitalRose, ACE is currently not supported in data residency EAP. However there is a workaround via override of
We will be assessing ACE support for future releases. We will keep you updated as we progress with this.
Thank you @SushantBista for the information. We will try the workaround in the mean time.