Hello,
We’re releasing Data Residency support for our apps imminently.
According to Log in with Atlassian account new Jira/Confluence customers will have access to the Data Residency feature within the host product from June 30th, and existing customers will have the feature turned on within the host product by Sept 30th.
Am I correct in thinking that new customers who region-pin their instance before installing our apps will get the region-specific version of our apps installed?
What happens to existing customers who were already region pinned before we released support for Data Residency in our app? At what point, if at all, will those Jira/Confluence instances start using the new region-specific domains specified in our app descriptor?
Jira site imports are considered by Atlassian’s internal infra to be a new Jira with no prior knowledge of previous app installations. It’s my understanding that this may cause a situation where a site import triggers a region-specific version of an app to be installed, where previously a “global” installation had been in place, so app data may “go missing” from the customer’s perspective. What is Atlassian doing to help vendors mitigate this problem?
Thanks for the update. My feedback below to your questions:
Am I correct in thinking that new customers who region-pin their instance before installing our apps will get the region-specific version of our apps installed?
Yes, that’s correct.
What happens to existing customers who were already region pinned before we released support for Data Residency in our app? At what point, if at all, will those Jira/Confluence instances start using the new region-specific domains specified in our app descriptor?
An app reinstall is required for existing instances that want to use new region-specific domains specified in your app descriptor.
Jira site imports are considered by Atlassian’s internal infra to be a new Jira with no prior knowledge of previous app installations. It’s my understanding that this may cause a situation where a site import triggers a region-specific version of an app to be installed, where previously a “global” installation had been in place, so app data may “go missing” from the customer’s perspective. What is Atlassian doing to help vendors mitigate this problem?
This is correct. We are currently assessing the best approach for handling various data lifecycle events including site imports. We will update you as we progress on this.
Am I correct in understanding that the customer would need to uninstall and reinstall the app via the Manage Apps screen? And then the region specific URLs we define in the app descriptor will be used?
How is this different to us releasing updates to the descriptor, which trigger uninstall and reinstall lifecycle events? Am I correct in understanding that the app manager treats these two scenarios differently?
Yes, it’s treated as a different scenario. For app version bumps (updated descriptor), there will be a ‘silent’ uninstall process without these lifecycle events sent out. Therefore, Connect will continue to use the existing installed region after an update, even if new regionBaseUrls have been added to the descriptor. However, once a ‘formal’ uninstall/reinstall is done, the relevant region specific URLs will apply.
Customers who don’t have a data residency requirement, but are provisioned in the EU or US for performance reasons install into the nearest supported region. This may provide performance improvements for end users.
That’s correct. Even though an instance is not region pinned, install preference will be set depending on the region that the instance is hosted on at the time of install.
Just cross-posting the answer from this other topic here to answer the question above:
Now, unfortunately it is not possible to distinguish between installation routed based off proximity versus an installation routed based off the product being pinned.
