Trigger runtime is US by default which is not GDPR compliant for EU countries
The ATLAS Trigger UI should let the user select the region for the realm deployment done in the background. At the moment it's not fair because (1) at no moment you're noticed the runtime will be in the US (and for UE countries it matters a lot, it's not GDPR compliant) and (2) it makes the nice ATLAS Trigger UI useless for UE countries...
We're forced to create a realm app manually to be able to select a local deployment. We appreciated the 'trigger' section on the ATLAS side. It's more integrated and makes following trigger operations easier. Now trigger logs and state is hidden deep within the realm section... not great !
1
vote
Bertrand Le Nistour
shared this idea