Talk:Infrastructure as code

Removing or correctly referencing the claim that IaC came from Ruby on Rails Twitter problems
Is there any reliable source really saying the IaC came as a solution to the Ruby on Rails lack of performace at twitter? Links are dead or behind paywall and I don't see these claims anywhere else. — Preceding unsigned comment added by Raul lapeira (talk • contribs) 16:38, 1 November 2020 (UTC)

Continuous configuration automation should be moved to its own page (March 2018)
Information from Continuous configuration automation tools should be moved to Continuous configuration automation page. March 2018 — Preceding unsigned comment added by 201.103.157.95 (talk) 23:05, 16 March 2018 (UTC)

Tone? added Advert template in March 2018
A lot of this article seems like it comes from marketing brochures and doesn't sound very factual. — Preceding unsigned comment added by 71.12.2.174 (talk) 20:40, 23 February 2016 (UTC)
 * Which bits? Some of it isn't how I'd write it myself, but there's nothing obvious here that doesn't stand up as factual. Viam Ferream (talk) 09:16, 24 February 2016 (UTC)
 * Not OP, but I thought the same thing when I read the overview. It sounds noticeably like marketing material. 213.23.230.154 (talk) 08:09, 5 August 2016 (UTC)
 * How about "In 2006 specifically, new challenges were brought to the forefront that shook the technology industry; the launch of Amazon Web Services’ Elastic Compute Cloud and the 1.0 version of Ruby on Rails just months before.[3]" - Really? "shook the technology industry"? Smac794 (talk) 16:01, 8 August 2016 (UTC)

I've been reading a lot on DevOps lately, and this article made me glaze over. After sixty agonizing seconds I still had no idea where in the cloud mosaic this piece belongs. Can someone please rescue from the buzzword salad at least one sharp idea on which to hang the article lead? &mdash; MaxEnt 21:57, 5 July 2016 (UTC)

"Infrastructure as Code" or "Infrastructure as code"?
Is it "Infrastructure as Code" or "Infrastructure as code" (in the title and body, respectively, last word of the three)?

If it is to follow Inversion of control, it should be "Infrastructure as code" (not "Infrastructure as Code").

It seems it was originally "Infrastructure as code" (it redirects).

--Mortense (talk) 16:07, 17 July 2018 (UTC)
 * Infrastructure as Code. It's no relation to inversion of control, it comes from Software as a Service, Software as a Product et al. Andy Dingley (talk) 14:58, 14 November 2018 (UTC)

Not a Sentence
"In 2006 specifically the launch of Amazon Web Services’ Elastic Compute Cloud and the 1.0 version of Ruby on Rails just months before."

This "sentence" has no main verb: In 2006 these launches... what? GeneCallahan (talk) 02:00, 23 October 2018 (UTC)

Merge Infrastructure as Software
Infrastructure as Software seems to be pretty much the same as Infrastructure as Code, except some marketing material might be trying to add some differentiation based on Turing completeness. I'm not sure if there is any content at Infrastructure as Software worth saving, but if there is, it should be merged here. MarioGom (talk) 10:45, 22 December 2021 (UTC)
 * Merge - I agree that the two articles are about the same subject.  Onel 5969  TT me 15:26, 8 January 2022 (UTC)
 * ✅: I have redirected it. The content have some COI/refspam issues, so I didn't merge anything, but anyone interested feel free to save any useful content there. MarioGom (talk) 23:47, 12 January 2022 (UTC)

Testing Infrastructure as Code
A section about testing infrastructure as code has been removed repeatedly due to the links I used as citations. I understand to keep links to the minimum but also that citations are needed. for example I added a list of methods to test infrastructure as code. in my understanding there should be a citation warranting the list. — Preceding unsigned comment added by WULRON (talk • contribs) 14:39, 2 May 2022 (UTC)


 * Reliable citations are needed, see WP:RS. Self published marketing materials such as company blog posts are not usable sources. MrOllie (talk) 14:52, 2 May 2022 (UTC)

Puppet: push and pull
Puppet works with a puppetmaster with the pull principle, but it can be work also via push using puppet bolt. Pier4r (talk) 15:26, 4 November 2022 (UTC)

Zeus: Vaporware As Code
By reading the github repository, I thing the Zeus link has been added for marketing purpose. There is no actually performing code, only claims of web3, crypto, ethereum with empty promises. I would recommand investigating this. — Preceding unsigned comment added by 2A01:E0A:4E1:97E0:BA20:9E6C:C7B4:BB7 (talk) 21:24, 4 February 2023 (UTC)

You're wrong dude, this code 100% works in production and all the cookbooks provide working apps on Kubernetes, do you have any background in infra or kubernetes? If you don't believe that send me an email @ alex@zeus.fyi and I'll demo it for you live and setup a paid account for you.

https://www.linkedin.com/in/alexandersgeorge/ — Preceding unsigned comment added by 104.175.196.33 (talk) 03:55, 15 February 2023 (UTC)


 * @[[User:范孝宗
 * @范孝宗@范凱富 2001:B011:2012:15A6:61CB:31BD:2668:7D1E (talk) 13:44, 23 November 2023 (UTC)

@范孝宗@范凱富 2001:B011:2012:15A6:61CB:31BD:2668:7D1E (talk) 13:42, 23 November 2023 (UTC)