Environments

An environment is one of your Aprimo instances: a place to try things out, a place to check them, or the live one everyone uses. You add each one once, and from then on Mochi can compare them, track their configuration, and carry changes between them.

How Mochi reaches an environment

Every environment carries its own address and credentials: the subdomain of the Aprimo instance, and a Client ID and secret that let Mochi talk to it on your behalf. You enter them once, when you add the environment. Mochi uses them to read your configuration and to update it when a run delivers a change.

Marking an environment as production

An environment can be marked Production. This is a live instance your team relies on, and a workspace can have several. Marking an environment as production is what gives your pipelines somewhere to finish: a pipeline ends at a production environment.

Reviewing an environment

Open an environment and choose Review. Mochi reads its current configuration and compares it to what you track. It shows you what's in the environment but not tracked yet, tracked items that were changed directly in that instance, and anything a tracked item points at that isn't there. Pick what you want and turn it into a change set.

A review is a read at a moment in time, not a live feed. When you want the latest, choose Rescan and Mochi reads the environment again.

Bringing an environment up to date

A change set becoming part of your configuration doesn't change any instance on its own. The Environments tab shows how far behind each one is, and Update brings it in line. That's the whole loop when you have a single environment: capture what changed, review it, then send it back when you're ready.

Where a pipeline is set up, an environment part-way along it takes its updates from the stage in front instead, so it's updated by running the pipeline rather than on its own. See Pipelines.