How did you manage role versions in your project?

Role version management in a project is usually related to change control in configuration and access, especially if roles define user or service permissions.

Approaches:

• Using version control systems (Git, SVN) — roles are described in configuration files (e.g., YAML, JSON, Terraform, Ansible) stored in a repository. Each change is committed with a description.

• Naming and semantic versioning — if roles evolve, versions can be used in the name or metadata, e.g., role_v1.0, role_v1.1.

• Deployment automation — CI/CD processes integrate role updates into pipelines, allowing rollback to previous versions if needed.

• Change documentation — a CHANGELOG or similar file records changes in roles.

Example: In Ansible, roles are stored in a separate folder, and changes are committed to Git. If necessary, you can switch to a specific commit or tag to use a particular version of the role.