What is the meaning of source artifacts that must be in a scripted form?

Quote from rom https://www.ibm.com/developerworks/library/a-devops6/index.html


The key prerequisite to versioning everything is that all source artifacts must be in a scripted form. This goes for the infrastructure, the data, configuration, and the application code. The only exception is for libraries and packages — JAR files and RPM packages, for example — that you use but never modify. After all source artifacts are scripted, you can easily version them.

What do they mean by "source artifacts must be in a scripted form"?

IMO these could be possible synonyms for scripted, in the context of your question here:

• in a textual format, which you can edit in some editor, like YAML, XML, JSON, PHP, etc.

• NOT in a binary format, the result of some build process (like a .EXE file, etc).

And I bet the reason for the "key prerequisite" (as in your quopted text), is that in the end you want to be able to perform some sort of comparison between 2 versions of such files. E.g. like a patch file (if usig GIT). Think about how a compare of 2 versions of a binary looks like, pretty sure every line is updated (or: all old lines are deleted, and all new lines are inserted).

This applies to pretty much any operating system, be it Linux, Windows, ..., or even zOS (aka good old mainframes).

StackExchange DevOps Q#3285, answer score: 3