← Back to all posts

Native Versioning for Policies, Contexts, and Blueprints

The ability to version contexts, policies, and blueprints would streamline management and workflows by allowing users to iterate on configurations without losing track of previous versions. Having versioned resources would help maintain flexibility when updating or rolling back settings, improving the overall efficiency and reliability of the process.

Workaround
Currently, the workaround involves manually creating new versions of resources, such as calling one version "V1" and the next "V2." These new versions are then attached to the stack, while the older ones are removed. This approach, though functional, requires extra steps and can be prone to human error.
Problem
The current method of managing versions by creating new resources complicates rollback, especially when the older versions are deleted. This is particularly problematic for policies, where there is a risk of inadvertently breaking everything by modifying an existing policy, causing potential disruptions across the system. Without version control, reversion to a stable state becomes cumbersome and error-prone.

Please authenticate to join the conversation.

Upvoters
Status

❌ Rejected

Board

💡 Feature Requests

Tags

Blueprints

Date

13 days ago

Subscribe to post

Get notified by email when there are changes.