Skip to main content

Native Versioning for Policies, Contexts, and Blueprints

Feature RequestsBlueprintsContextsPolicies

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
Problem
Status: ❌ Rejected1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    Feb 11

    Hi David,

    Thanks for the detailed feedback about versioning policies, contexts, and blueprints. I understand the frustration with the current manual approach of creating "V1" and "V2" versions.

    The good news is that Spacelift already supports robust versioning for these resources through our code-first approach:

    For Policies:

    • Store your Rego policies in Git repositories
    • Use our Terraform provider to manage policy attachments
    • Leverage Git tags/branches for versioning and rollbacks
    • This gives you full audit trails, peer review, and collaboration

    For Contexts:

    • Manage contexts programmatically via the Spacelift Terraform provider
    • Version your context configurations in Git alongside your infrastructure code
    • Use Terraform's state management for safe updates and rollbacks

    This approach aligns with infrastructure-as-code best practices and gives you more powerful versioning capabilities than any UI-based system could provide. You get Git's full history, branching, merging, and collaboration features.

    On the other hand, blueprints are quite special here and we’ll soon be launching something that you will probably like a lot. Please stay tuned!