Skip to main content

Versioned mounted files

Feature RequestsContexts

It would be nice to have versioned mounted files in contexts (ie .tfvars files) and be able to change between versions (or at least show differences between them).

Plus having a way of bind a stack execution with a mounted file version in order to see what set of variables is applying in that stack trigger

Status: 🗑️ Archived3 comments

Log in to comment and vote

Comments3

  • Natalia Gazda

    Team•

    Sep 16

    Thanks for raising this, and to everyone who upvoted. It's been open for a while without gaining much upvotes, so I’m closing it for now while we focus on higher-priority work.

    It's not gone for good. If demand grows or priorities shift, we may revisit. If it still matters to you, leave a comment with your use case so we can gauge interest.

    Thanks for the feature request :)

  • Olive Gizmo

    •

    Sep 6, 2024

    Hi @Natalia Gazda! I’ll try my best to explain myself!

    Currently in Spacelift we are running dozens of single-repo multistacks, meaning that we are dividing a single environment (repository) into multiple stacks. That turns out in having a common .tfvars file for all the stacks within an environment where we are declaring the common variables between stacks.

    Since with a monorepo we need to point stacks to folders within the repository we can’t get a nice way to handle the tfvars files because is out of the structure of the folders where stacks are pointing causing an operational risk because the tfvars in the repo could be (or not) the same tfvars mounted in Spacelift… and this is where this feature could be useful.

    With a way of versioning the mounted files a member of our team could be able to change some variables and run the stacks underneath, and a few hours later a colleague could check if there was any kind of change and be sure that all the stacks mounting that file are using the latest version or even rollback to a previous version of the tfvars file because there was a mistake in some variable.

    WIth a feature like this we could be able also to see the version of the tfvars file applied within a stack execution, whis is a thing we are doing right now printing the whole tfvars in the execution with a prehook.

    I hope i was helpful, if not don’t hesitate to ask me for an extended version :)

  • Natalia Gazda

    Team•

    Sep 5, 2024

    @Miguel García thanks for submitting that! Before I can give you more feedback, would you mind sharing your use-cases for the versioning? Thanks!