This infrastructure is managed by Fleet Manager
The infrastructure settings are automatically managed.
Controls how the Project deployer behaves when bundles deployed on this infrastructure are not qualified or approved in Dataiku Govern.
URL should be http[s]://host[:port]. A URL suffix is unexpected and will likely not work.
URL should be http[s]://host[:port]. A URL suffix is unexpected and will likely not work.
(Optional) This URL will be used on screen for user navigation. The above URL will be used by the Deployer to communicate with the Automation node.
List of Automation nodes with their URL, optional External URL, and admin API key
Add from Nodes Directory: 
Group name View Deploy Admin  
No group is granted access to this infrastructure
{{perm.group}}
To manage groups go to DSS global administration.

Connection remapping

Remap connection names declared in the bundles to connections existing on the infrastructure.

Containerized execution remapping

Remap containerized execution configs declared in the bundles to configs existing on the infrastructure.

Multi-node deployments

Set the whole automation instance as not alive during a deployment update. If unchecked, only the deployed project is set as not alive.
Delay between the disabling of the instance/deployed project and the actual update (must be consistent with the load balancer configuration)

Permissions propagation

Policy for permissions propagation from the bundle to the Automation node (only applicable on the first deployment)
Do not propagate any permission, the deploying user will be set as project owner.
Replicate the permissions from the design nodes and grant to the design project owner admin permissions (provided the groups and users already exist on the Automation node).
Add the design project owner, used groups and users from the bundle to the Automation project with only 'Read project content' & 'Run scenarios' rights (provided the groups and users already exist on the Automation node)

Webapps

On a deployment creation/update, it will stop and restart all running webapps. Every auto-start webapp will be started as well.

Deploy as user

Deploy project with a selected user. If not enabled, the user requesting the deployment will be used.
An override user must be specified for deployment to be possible. If no default, this requires to set a non empty user for each deployed project.
Default user for deployments. Overridable per project.

Run as user of Scenarios and Webapps

On creation of a scenario or a webapp, override its 'run as' user.
Default run as user to set for new webapps and scenarios. Overridable per project.

Project Standards control

If a check encounters an execution error, use this level of severity
If checked, allow deployment of bundles where the user has skipped Project Standards during bundle creation.
If checked, allow deployment of bundles published before the Project Standards feature was available. Otherwise, users will have to create a new bundle with a Project Standards report to deploy.