Comments (2)
I have not been in contact with anyone from the Armory repo. I've put a lot of effort into creating a definitive resources rather than just rely on json blobs which the other one uses
from terraform-provider-spinnaker.
The armory one was actually an experiment to see if there was enough interest to develop a product around such a provider. It works, uses the public API, and does pretty well for what it is. However, most of our customers use Dinghy - our corporate solution around GitOps style workflows OR some internal custom mechanism (aka the spin-cli tools & a job). @jgramoll has created is pretty impressive and is much more involved. A few thoughts on maybe some differences (not saying which is better) as they handle the problem with different methods.
- This provider uses a custom client vs. the spinnaker maintained Go client. https://github.com/spinnaker/spin is the supported go client. An example impact: things like basic auth doesn't work in this provider where the armory one just uses the gate config file from spin. Other impacts would be long term changes in the API causing breaking changes in this provider. It's much more... "manual" to maintain & keep in sync.
- One advantage on this one - you get POTENTIALLY code completion and other syntax "help". Aka you can use IntelliJ terraform stuff to auto complete syntax (though not tested that with a manually managed provider). There are fields for everything you need to fill out.
- Though more "terraform" in nature with the different resources to control pipelines, triggers, etc. there is another caution flag similar to the challenges similar to the V1 vs. V2 provider. V2 fully allows manifests thus a large amount of flexibility and capability. I always worry about Terraform's very strict typing of resources. It's similar to the Terraform handling of k8s manifests and why many k8s users don't use the native kubernetes provider. For advanced users, it's quite possible the JSON version is more "useful". PARTICULARLY if your team isn't super terraform native, and just wants to do a "update the manifest and apply" kinda thing.
from terraform-provider-spinnaker.
Related Issues (7)
- Docker trigger support HOT 6
- [Request] Spinnaker Patch Manifest Resource
- Apply fails: invalid character '<' looking for beginning of value HOT 1
- Expected artifacts and provider-specific stages HOT 1
- Thanks for the provider but i have problem when i want to provision template and template_config HOT 7
- Support for M1 Chips
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-spinnaker.