5 ms·
> Gold Fig Labs: The startup is building a tool for version control on settings pages. The founders come from Firebase, where they were both early employees. Th
by _hardwaregeek 7y ago
> Gold Fig Labs: The startup is building a tool for version control on settings pages. The founders come from Firebase, where they were both early employees. The company has signed up 60 companies in the last five weeks, including “multi-billion-dollar tech companies.
I've been setting up some pipelines at work. I was thinking recently, "huh, these pipelines aren't easily version controlled at all". Unless you use something that is completely configurable by text, which is pretty hard to accomplish, then it's basically impossible to get a snapshot of your services. It's even harder to roll stuff back. Or branch it off and test out a new configuration. I'd wager that a lot of issues in production are configuration related, simply because it's harder to introspect and code review versus code changes. Hopefully that can be fixed.
- KptMarchewa 7y agoMaybe I don't understand what you're trying to achieve, but doesn't Gitlab CI fulfill that role? Your versioning system is essentially git. Branching is done trivially, rolling stuff back is running deploy pipeline from older branch or tag.
- _hardwaregeek 7y agoI'm talking about versioning infrastructure. So let's say you have a setup with a load balancer, three compute VMs and two database instances. You modify the config to make it three compute VMs and three database instances, but suddenly something goes wrong! Can you roll back your infrastructure easily?
- lazyant 7y agoThis is a standard "infrastructure as code" task for devops/SREs/whatever , for ex using Terraform
- GordonS 7y agoAssuming you mean CI/CD pipelines, with at least Azure DevOps, Travis and AppVeyor, pipelines are configured using YAML files, which are themselves checked into source control (e.g. git), so they are versioned just the same as any other files. Azure DevOps supports both a graphical UI and YAML files. Pipelines created with the UI are versioned within Azure DevOps, rather than source control. I get the impression that the UI is considered deprecated, even if Microsoft haven't explicitly said so.
- _hardwaregeek 7y agoMore data processing than CI/CD. But really all infrastructure config should be versioned. Can you version an AWS Lambda config? I'm genuinely asking.
- dragonwriter 7y agoWhile AWS services support multiple routes of control, infrastructure-as-code via CloudFormation JSON/YAML which can be managed like source code is one of the preferred ways.
- GordonS 7y agoNot sure about AWS specifically, but on Azure you have several methods available to define your infrastructure as code (IaC), including JSON-based ARM templates[0]. AWS and GCP must have similar IaC capabilities. [0] https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authoring-templates https://docs.microsoft.com/en-us/azure/azure-resource-manage...
- marcinzm 7y ago>which is pretty hard to accomplish At my last two companies we used Terraform and Kubernetes with everything stored as text in git. Has worked pretty well.