Over the last 30 years, the Configuration Management community has learned that using a declarative approach to resource management is beneficial for both stability and change management. How does this apply to the new paradigm of Kubernetes deployments?
YAML has become the de-facto standard to express resources in many fields linked to DevOps practices. What are YAML's strengths and weaknesses, and what are the other options going forward?
| $ ./shellvar.lua ensure=present target=/tmp/foo key=foo value=bar | |
| Saved 1 file(s) |
| (1..100).each do |i| | |
| fizz = (i % 3 == 0) ? 'Fizz' : '' | |
| buzz = (i % 5 == 0) ? 'Buzz' : '' | |
| num = (i % 3 == 0 || i % 5 == 0) ? '' : i | |
| puts ("#{num}#{fizz}#{buzz}") | |
| end |
| $ ./src/augtool -I lenses/ -f test.auglua | |
| Hello, world | |
| 1.4.0 | |
| 1041 |
| module Test = | |
| let lns = [ key "a" . store "b" ] | |
| let _ = print_regexp (lens_ktype lns) |
| #!/usr/bin/env ruby | |
| require 'jgrep' | |
| def get_facts(facter_version, filter) | |
| filter_str = filter.map { |f| f.map { |k,v | "#{k}=#{v}" }.join(' and ') }.join(' or ') | |
| jsons = Dir.glob("facts/#{facter_version}/*.facts").map { |f| File.read(f) } | |
| json = "[#{jsons.join(',')}]\n" | |
| JGrep.jgrep(json, filter_str) |
I hereby claim:
To claim this, I am signing this object:
| $ cat /tmp/test.sh | |
| echo foo | tee bar.txt || TRUC_EGAL=baz | |
| $ augtool -I lenses/ -Ast "Shellvars.lns incl /tmp/test.sh" set /files/tmp/test.sh/@command/@pipe/@command cat | |
| Saved 1 file(s) | |
| $ cat /tmp/test.sh | |
| echo foo | cat bar.txt || TRUC_EGAL=baz |
| { "dict" | |
| { "entry" = "key" | |
| { "#comment" = "my key" } | |
| { "string" = "value" | |
| { "#comment" = "my value" } | |
| } | |
| } | |
| { "#comment" = "after value" } | |
| { "entry" = "key2" | |
| { "string" = "val2" } } } |
| augeas_file { '/tmp/abc': | |
| base => '/tmp/abc.base', | |
| } | |
| augeas { 'foo': | |
| incl => '/tmp/abc', | |
| lens => 'Shellvars.lns', | |
| changes => ['set foo bar'], | |
| } |