Page tree

 

Contents:


The Trifacta platform supports multiple types of platform environments. This section describes how to enable and configure the different types of platform environments and assign users to them.

Tip: When you initially set up a platform instance, you should decide whether it is a Dev instance, a Prod instance or both. Details are below.

NOTE: Assignment of roles must be executed through the Admin Settings page. You cannot assign roles through CLI or API commands.

Platform Instance TypeDescriptionUser ManagementDefault?
Development (Dev) onlyA Development instance of the platform is used to build and test your flows and recipes until they are ready for operational use in production.

All users can build and execute flows.

No users can access the Deployments area.

Yes
Production (Prod) only

A Production instance serves to host production versions of your flows, to manage the versions that are in use, and to execute jobs. It is primarily a read-only instance of the platform. You cannot access the Transformer page to modify your recipes in a Production instance.

When a flow is ready for production use, you can export the flow from the Dev instance and import it into the Prod instance.

For more information, see Overview of Deployment Management .

No users can build and execute flows.

All users access the Deployments area.

 

No

Both

(All-in-One)

A Development environment can be configured to serve as both instance types.Users can access the Deployments area only if the Deployments role has been added to their accounts.No

Enable Dev-Only Environment

No deployment management configuration is required. 

NOTE: Do not include the Deployment role in any users accounts. See Manage Users.

Enable Prod-Only Environment

If you are installing separate instances of the  Trifacta platform to serve as Dev/Test and Prod environments, you can configure the Prod environment to serve only production purposes. Users who are permitted access to this environment can create and manage deployments, releases within them, and jobs triggered for these releases. 

Tip: Separate Dev and Prod platform instances is recommended.

By default, the installed instance of the platform is configured as a Development instance. To configure the installed platform to operate as a Production instance, please complete the following steps.

NOTE: If you are enabling a Production-only instance of the platform, you should verify that you have deployed sufficient cluster resources for executing jobs and have sufficient nodes and users in your Trifacta license to support it. For more information, see Overview of Deployment Management.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Configure the following setting to be true:

    "deploymentManagement.enabled" : true,
  3. Save your changes and restart the platform.

User Management for Prod-only

You must create accounts in the Prod instance for users who are to be permitted to create and manage deployments. 

Tip: You should limit the number of users who can access a Production environment.

NOTE: Any user who has access to a Production-only instance of the platform can perform all deployment-related actions in the environment. The Deployment role does not apply. For more information, see Manage Users.

Enable All-in-One Environment

In this environment, individual user accounts may access development and testing features of the platform or the deployment management features of the platform, but not both. A user is a development user or a production user, based upon roles in the user's account. 

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Configure the following setting to be false:

    "deploymentManagement.enabled" : false,
  3. Save your changes and restart the platform.

User management for All-in-One environment

In this environment, access to deployment management is determined by the presence of the Deployment role in a user's account:

When deploymentManagement.enabled=false:

Deployment roleDescription
Not present in the account

User experiences the platform instance as a default Dev experience.

User can create flows, recipes, and datasets, as well as run jobs on both a scheduled and ad-hoc basis.

Present in the account

User experiences the platform instance as a Prod environment.

User can create and manage deployments and their releases. User can review connections and flows, although interaction may be limited.

NOTE: Users should avoid making changes to flows in a Production environment. When a new release of a flow is imported, those changes are lost.

Switching roles

In an All-in-One environment, administrators can change account permissions to enable or disable access to Prod features.
  • Administrators should not apply these permission changes to admin accounts; use a separate account instead.
  • If you switch the Deployment role on a single account, changes that you make to a Dev version of a flow are not automatically applied to a Prod version of the same flow, and vice-versa. You must still export the flow from one environment and import into the other to see any changes. 

This page has no comments.