Skip to main content
Version: 5.4

Versioning

Versioning of Configurations

Versioning of configurations is essential to make the operation of the OPC Router secure and traceable in enterprise environments.
It offers several advantages:
Traceability: All changes to the system configuration are documented, so you can always see who made what changes and when.
Security: In the event of problems or misconfigurations, it is possible to quickly restore an earlier, stable version.
Compliance: Many industries have regulatory requirements that require documentation and traceability of system changes.

Integrated Versioning in the OPC Router

The OPC Router supports Git internally and uses YAML configuration files, providing effective configuration management and versioning. This built-in versioning provides an out-of-the-box solution for tracking changes and rolling back to previous versions.

Benefits of integrated versioning

Ease of use: No additional tools or setup required.
Automatic versioning: Every change is automatically versioned and documented.
Fast Recovery: If necessary, it's easy to revert to a previous version.

Extensions through integration with hosted Git servers

Integrated versioning can be made even more powerful by connecting to hosted Git servers such as GitHub, Bitbucket, or Microsoft Azure DevOps. These external repositories provide additional features such as centralized management, advanced access control, and comprehensive change tracking.

Implementation Strategies Integration with Hosted Git Servers

Benefits: Centralized management, access control, and comprehensive change tracking. Implementation: Connect the OPC Router's internal Git system to a hosted Git server (e.g., GitHub, Bitbucket, Microsoft Azure DevOps).

warning

It is important to ensure that the repositories are private to prevent unauthorized access.

Automated versioning

Supported by the OPC Router: Automatic versioning and change tracking directly in the OPC router.
Automated Backups: Set up automated backup processes to regularly back up configuration files.

Best Practices

To take full advantage of versioning, the following best practices should be followed:

Commits: Commit the current configuration to the local Git repository on a regular basis.
Pushes: Push the commits to the hosted Git server on a regular basis, e.g. daily or after every significant change. This can be done manually using a Git client such as Git Console, GitHub Desktop, or SourceTree.
Keep change logs: Keep a detailed log of all changes made, including the date, time, and name of the person responsible.
Use tools that can automate this logging.
Test environment: Implement a test environment where changes can be validated before being deployed to production.
Use staging environments to gradually introduce changes and monitor their effects.
Security of secrets: Secrets or passwords should never be stored in the Git repository. The OPC Router always stores secrets in a separate local vault to ensure that they are not versioned.

Practical Implementation Integration with Hosted Git Servers

Setting up the Git server: Set up a hosted Git server (e.g., GitHub, Bitbucket, Microsoft Azure DevOps) to manage the configuration files. Make sure the repositories are private.
Connect the OPC Router: Configure the OPC router to use the hosted Git server for versioning.
Management and Monitoring: Use the Git server to manage, track, and monitor all configuration changes.

Automated versioning

Enable in OPC Router: Enable automatic versioning and change tracking in the OPC Router.
Automated Commits: Set up commit routines to back up configuration files on a regular basis.
Push Processes: Manually or automatically push commits to the hosted Git server.
Monitoring: Regularly checking and maintaining version control systems to ensure integrity and availability.

Summary

Configuration versioning is an essential part of operating the OPC Router in enterprise environments.

It ensures that changes are traceable, increases security through easy rollback, and meets regulatory requirements.

By leveraging the OPC Router's built-in versioning and extending it with hosted Git servers, organizations can significantly improve the reliability and maintainability of their OPC Router instances.