spaceliftArchived
4 messages
jaysunalmost 2 years ago(edited)
we just adopted Atlantis, and while it seems to do the job.. we’re not super impressed with its capabilities. we MIGHT look into paid products like spacelift, but curious what a ballpark $ would be for the enterprise plan. I’m sure that’s a hard question to answer without specifics, but some general ballpark #s for an environment like this would be much appreciated:
• self hosted GHA via ARC
• ~ 40 terraform repos
• ~ 40 ish users who submit PRs against those repos, but only 10 ish who actually need to support the infra
TY!
• self hosted GHA via ARC
• ~ 40 terraform repos
• ~ 40 ish users who submit PRs against those repos, but only 10 ish who actually need to support the infra
TY!
Slackbotalmost 2 years ago
Upgrade to reconnect this channel
Your team recently switched to a free plan. Spacelift has been removed from this channel. To automatically reconnect this channel, upgrade to a paid plan by Sunday, May 5th.
Your team recently switched to a free plan. Spacelift has been removed from this channel. To automatically reconnect this channel, upgrade to a paid plan by Sunday, May 5th.
johncblandiialmost 2 years ago
Is there any guidance published regarding splitting an admin stack?
context: our plat admin stack is massive now. it handles dev, beta, qa, and prod for a lot of stacks. this takes a long while to run. i'd like to split stacks by stage and am wondering if we would have any issues (namely would stacks destroy and recreate) and if we could just import into the new admin stack.
context: our plat admin stack is massive now. it handles dev, beta, qa, and prod for a lot of stacks. this takes a long while to run. i'd like to split stacks by stage and am wondering if we would have any issues (namely would stacks destroy and recreate) and if we could just import into the new admin stack.
johncblandiialmost 2 years ago
Any thoughts on how Spacelift manages squash commits?
We had a scenario where commit A ran (created 3 ssm params) and commit B ran (deleted those 3).
I've seen some seemingly weird nuance to how commits are handled where it uses hashes from PR and not solely the squash commit id.
is this an issue with the policy or something deeper in spacelift?
We had a scenario where commit A ran (created 3 ssm params) and commit B ran (deleted those 3).
I've seen some seemingly weird nuance to how commits are handled where it uses hashes from PR and not solely the squash commit id.
is this an issue with the policy or something deeper in spacelift?