Segura allows moving configurations between different environments (such as testing and production environments) using the backup and restore mechanisms available in the Orbit module. Although there is no native one-click configuration promotion functionality, it is possible to replicate parameterizations from one environment to another manually or automatically.
Functionalities
- Exporting configurations tested in the source environment.
- Applying these configurations to another environment.
- Support for automation via scripts, with commands already available in the CLI.
- Independence from agents or external tools.
Applicability
- Replication of approved configurations from homologation to production.
- Synchronization between segregated environments.
- Deployment of contingency environments with standardized configurations.
Use cases
- DevOps teams that want to reuse parameterizations.
- Clients with multiple Segura instances (for example, end-customer, partner, and testing environments).
- Security teams that want to validate and replicate consistent policies.
Basic flow
- Generate backup in the source environment: The administrator generates a backup containing the desired configurations.
- Transfer the file to the destination environment: This process can be done manually or via automation.
- Restore the backup in the destination environment: The backup is restored in the production environment, replicating the validated configurations.
Make sure to review environment-specific parameters (such as URLs, integrations, and tokens) after restoration.
Post-condition
The replicated configurations will be active in the destination environment. After application, integrity verification and additional testing in the production environment are recommended.
Conclusion
Although Segura doesn't offer automatic synchronization functionality between environments, the backup and restore mechanisms allow secure achievement of this goal. The implementation of this flow depends on the client.