-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
2.4
-
None
-
False
-
-
False
Description:
When a JT is executed using an Execution node and if the EE is not present on the execution node, it should not make an outbound connection, the controller should be capable enough to load the required EE into Execution as a part of JT execution.
Env:
Controller -> can connect to Ex node.
Execution -> Only controller can make inbound connection, no outbound connections allowed.
Registry -> AH/Red Hat registry access is only limited to controller machine.
Why customer wants this?
We have a very strict network architecture and try to make it possible to use automation for every user in the company even in not directly connected or routed networks without violating network requirements we have to follow.