Allow Network Peering to be used by Atlas Triggers / Realm Apps
What is the problem that needs to be solved? Some users want to receive outgoing network connections (e.g. with HTTP/HTTPS traffic) from Atlas (Atlas Triggers / Realm Apps) via their configured Network Peering, i.e. via private IP address space (so that everything is kept in private IP address space and nobody outside could reach it). Example: customer would like to have Atlas Trigger / Realm App which will notify (via HTTP) some of customer's internal system(s) about a change/trigger.
Why is it a problem? (the pain) Current Atlas (Atlas Triggers / Realm Apps) behavior does not allow to use private IP address space for such outgoing network connections.