Thanks for the idea! Curious to dig deeper here—what’s the real job you’re trying to get done?
Dynamic context assignment per run sounds powerful, but potentially brittle—especially for things like credentials or mounted files. Is the goal to vary behavior by branch? Or are you trying to simplify how stacks are reused across PRs or environments?
We’d love to understand more—especially if this is tied to Ansible workflows. We know we haven’t nailed those yet and want to offer the right building blocks, not just bolt-ons. What would success look like for you here?
Maroon Telescope
•
May 12, 2025
Thanks for looking into it - the problem with myself is always that I have ideas but don’t formulate those very well and thus I don’t know exactly what I was thinking back then ;-(
But I think I remember mostly what was going on here.
We created contexts with secrets and environment variables needed in Ansible as it should be. The issue I ran into was that I wanted to provide specific “testing” variables (so for an sandbox vs. production) to the ansible runs and I did not figure how to do that.
That said a colleague already told me that he thinks that should be possible with policies. So we need to look into those now.
TBH the thing is that we currently don’t use Spacelift for our Ansible Jobs. Because of other duties I need to look into those more and the hustly to build our own images for Ansible with all collections and whatelse is not my focus right now sadly.
Log in to comment and vote
Comments2
Black Breeze
May 10, 2025
Thanks for the idea! Curious to dig deeper here—what’s the real job you’re trying to get done?
Dynamic context assignment per run sounds powerful, but potentially brittle—especially for things like credentials or mounted files. Is the goal to vary behavior by branch? Or are you trying to simplify how stacks are reused across PRs or environments?
We’d love to understand more—especially if this is tied to Ansible workflows. We know we haven’t nailed those yet and want to offer the right building blocks, not just bolt-ons. What would success look like for you here?
Maroon Telescope
May 12, 2025
Thanks for looking into it - the problem with myself is always that I have ideas but don’t formulate those very well and thus I don’t know exactly what I was thinking back then ;-(
But I think I remember mostly what was going on here.
We created contexts with secrets and environment variables needed in Ansible as it should be. The issue I ran into was that I wanted to provide specific “testing” variables (so for an sandbox vs. production) to the ansible runs and I did not figure how to do that.
That said a colleague already told me that he thinks that should be possible with policies. So we need to look into those now.
TBH the thing is that we currently don’t use Spacelift for our Ansible Jobs. Because of other duties I need to look into those more and the hustly to build our own images for Ansible with all collections and whatelse is not my focus right now sadly.