Browse the docs
How Trinium works

Connections and access

A connection is a named, saved set of settings for one system. A node names the connection; the credentials themselves never enter a pipeline.

Connectors and connections

A connector is a kind of system Trinium can reach, such as PostgreSQL or Amazon S3. A connection is one configured instance of it, with its address and credentials. Each connector has a page in Connectors listing what its form asks for and what its Test checks.

Credentials are stored encrypted with the instance's master key and are never shown again after you save them. A pipeline and its versions never carry them, and a portable backup leaves them out.

Staging and Production

Every connection has a Staging side, which it needs, and an optional Production side with values of its own. A run uses the side of the environment it runs in. Production settings cannot be saved without Staging settings, and a Production run on a connection with no Production side fails, naming it.

Who may use it

  • A shared connection is created by an administrator and has an access list: people, workspaces, or everyone. Being on the list lets you use the connection in pipelines and run them in Staging. A grant to a workspace works only for that workspace's pipelines; a grant to a person follows that person.
  • Production access is a second, separate permission on the same list. Deploying to Production, running there and scheduling there need it on every connection the version uses. Nobody has it implicitly, administrators included: an administrator adds themselves, which leaves a record.
  • A personal connection is yours. Nobody else may run, deploy or schedule a pipeline through it.
  • The list is checked where a person acts: when a pipeline is run, deployed or scheduled, not only when a node is configured. A Production schedule keeps firing after its creator loses access, so it never stops silently.

Testing and deleting

Test signs in with the side you are looking at and says what the system answered. A connection used by a pipeline's draft or its Staging or Production version cannot be deleted; the refusal names what uses it.