Documentation Index

Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt

Use this file to discover all available pages before exploring further.

Move configurations between environments

Prev Next

Segura® lets you move configurations between environments (such as testing and production) using the backup and restore mechanisms in the Orbit module. There is no native one-click configuration promotion, but these mechanisms let you securely replicate settings from one environment to another, manually or automatically. How you implement the flow depends on your environment.

What this supports

This approach supports the following:

  • Exporting configurations tested in the source environment.
  • Applying those configurations to another environment.
  • Automating the workflow with scripts, using commands available in the CLI.
  • Operating without agents or external tools.

Applicability

Use this process in scenarios such as:

  • Replicating approved configurations from a test environment to production.
  • Synchronizing configuration between segregated environments.
  • Deploying contingency environments with standardized configurations.

Use cases

This process is useful for:

  • DevOps teams that want to reuse configurations.
  • Customers with multiple Segura® instances (for example, end-customer, partner, and testing environments).
  • Security teams that want to validate and replicate consistent policies.

Steps

To move a configuration from a source to a target environment:

  1. Generate a backup in the source environment. The administrator generates a backup containing the desired configurations.
  2. Transfer the file to the target environment. Do this manually or through automation.
  3. Restore the backup in the target environment. Restore the backup to replicate the validated configurations.
Info

Review environment-specific parameters (such as URLs, integrations, and tokens) after the restore.

Expected results