GitHub - bedag/spruce: A BOSH template merge tool

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

 * .---. ,---. ,---. .-. .-. ,--, ,---. *
/.\ ( .-._)| .-.\ | .-.\ | | | |.' .') | .-' /.\
/..'\ (_) \ | |-' )| `-'/ | | | || |(_) | `-. /..'\
/'.'\ _ \ \ | |--' | ( | | | |\ \ | .-' /'.'\
/.''.'\ ( `-' ) | | | |\ \ | `-')| \ `-. | `--. /.''.'\
/.'.'.\ `----' /( |_| \)\`---(_) \____\/( __.' /.'.'.\
"'""""/'.''.'.\""'"'""""""(__)""""""""(__)"""""""""""""(__)""'""""/'.''.'.\""'"'"
^^^[_]^^^ ^^^[_]^^^

( We'll be in #spruce)

Introducing Spruce

spruce is a general purpose YAML & JSON merging tool.

It is designed to be an intuitive utility for merging YAML/JSON templates together to generate complicated YAML/JSON config files in a repeatable fashion. It can be used to stitch together some generic/top level definitions for the config and pull in overrides for site-specific configurations to DRY your configs up as much as possible.

How do I get started?

spruce is available via Homebrew, just brew tap starkandwayne/cf; brew install spruce

Alternatively, you can download a prebuilt binaries for 64-bit Linux, or Mac OS X

How do I compile from source?

Install Go, e.g. on Ubuntu sudo snap install --classic go
Fetch sources via go get github.com/bedag/spruce
Change current directory to the source root cd ~/go/src/github.com/bedag/spruce/
Compile and execute tests make all

A Quick Example

# Let's build the first yaml file we will merge
$ cat <<EOF first.ymlsome_data: this will be overwritten latera_random_map: key1: some dataheres_an_array:- first elementEOF# and now build the second yaml file to merge on top of it
$ cat <<EOF second.ymlsome_data: 42a_random_map: key2: adding more dataheres_an_array:- (( prepend ))- zeroth elementmore_data: 84# what happens when we spruce merge?$ spruce merge first.yml second.ymla_random_map: key1: some data key2: adding more dataheres_an_array:- zeroth element- first elementmore_data: 84some_data: 42

The data in second.yml is overlayed on top of the data in first.yml. Check out the merge semantics and array merging for more info on how that was done. Or, check out [this example on play.spruce.cf][play.spruce-example]

Documentation

What else can Spruce do for you?

spruce doesn't just stop at merging datastructures together. It also has the following helpful subcommands:

spruce diff - Allows you to get a useful diff of two YAML files, to see where they differ semantically. This is more than a simple diff tool, as it examines the functional differences, rather than just textual (e.g. key-ordering differences would be ignored)

spruce json - Allows you to convert a YAML document into JSON, for consumption by something that requires a JSON input. spruce merge will handle both YAML + JSON documents, but produce only YAML output.

spruce vaultinfo - Takes a list of files that would be merged together, and analyzes what paths in Vault would be looked up. Useful for determining explicitly what access an automated process might need to Vault to obtain the right credentials, and nothing more. Also useful if you need to audit what credentials your configs are retrieving for a system..

License

Licensed under the MIT License

Name		Name	Last commit message	Last commit date
.github		.github
assets		assets
cmd/spruce		cmd/spruce
doc		doc
examples		examples
log		log
tests		tests
vendor		vendor
.gitignore		.gitignore
.travis.yml		.travis.yml
.whitesource		.whitesource
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
diff.go		diff.go
diff_test.go		diff_test.go
errors.go		errors.go
evaluator.go		evaluator.go
evaluator_test.go		evaluator_test.go
go.mod		go.mod
go.sum		go.sum
json.go		json.go
merge.go		merge.go
merge_test.go		merge_test.go
op_aws.go		op_aws.go
op_base64.go		op_base64.go
op_base64_decode.go		op_base64_decode.go
op_calc.go		op_calc.go
op_cartesian_product.go		op_cartesian_product.go
op_concat.go		op_concat.go
op_defer.go		op_defer.go
op_empty.go		op_empty.go
op_file.go		op_file.go
op_grab.go		op_grab.go
op_inject.go		op_inject.go
op_ips.go		op_ips.go
op_join.go		op_join.go
op_keys.go		op_keys.go
op_load.go		op_load.go
op_negate.go		op_negate.go
op_null.go		op_null.go
op_param.go		op_param.go
op_prune.go		op_prune.go
op_shuffle.go		op_shuffle.go
op_sort.go		op_sort.go
op_static_ips.go		op_static_ips.go
op_stringify.go		op_stringify.go
op_vault.go		op_vault.go
operator.go		operator.go
operator_test.go		operator_test.go
sort_test.go		sort_test.go
vault_test.go		vault_test.go

Name		Name	Last commit message	Last commit date
.github		.github
assets		assets
cmd/spruce		cmd/spruce
doc		doc
examples		examples
log		log
tests		tests
vendor		vendor
.gitignore		.gitignore
.travis.yml		.travis.yml
.whitesource		.whitesource
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
diff.go		diff.go
diff_test.go		diff_test.go
errors.go		errors.go
evaluator.go		evaluator.go
evaluator_test.go		evaluator_test.go
go.mod		go.mod
go.sum		go.sum
json.go		json.go
merge.go		merge.go
merge_test.go		merge_test.go
op_aws.go		op_aws.go
op_base64.go		op_base64.go
op_base64_decode.go		op_base64_decode.go
op_calc.go		op_calc.go
op_cartesian_product.go		op_cartesian_product.go
op_concat.go		op_concat.go
op_defer.go		op_defer.go
op_empty.go		op_empty.go
op_file.go		op_file.go
op_grab.go		op_grab.go
op_inject.go		op_inject.go
op_ips.go		op_ips.go
op_join.go		op_join.go
op_keys.go		op_keys.go
op_load.go		op_load.go
op_negate.go		op_negate.go
op_null.go		op_null.go
op_param.go		op_param.go
op_prune.go		op_prune.go
op_shuffle.go		op_shuffle.go
op_sort.go		op_sort.go
op_static_ips.go		op_static_ips.go
op_stringify.go		op_stringify.go
op_vault.go		op_vault.go
operator.go		operator.go
operator_test.go		operator_test.go
sort_test.go		sort_test.go
vault_test.go		vault_test.go

Name		Name	Last commit message	Last commit date
.github		.github
assets		assets
cmd/spruce		cmd/spruce
doc		doc
examples		examples
log		log
tests		tests
vendor		vendor
.gitignore		.gitignore
.travis.yml		.travis.yml
.whitesource		.whitesource
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
diff.go		diff.go
diff_test.go		diff_test.go
errors.go		errors.go
evaluator.go		evaluator.go
evaluator_test.go		evaluator_test.go
go.mod		go.mod
go.sum		go.sum
json.go		json.go
merge.go		merge.go
merge_test.go		merge_test.go
op_aws.go		op_aws.go
op_base64.go		op_base64.go
op_base64_decode.go		op_base64_decode.go
op_calc.go		op_calc.go
op_cartesian_product.go		op_cartesian_product.go
op_concat.go		op_concat.go
op_defer.go		op_defer.go
op_empty.go		op_empty.go
op_file.go		op_file.go
op_grab.go		op_grab.go
op_inject.go		op_inject.go
op_ips.go		op_ips.go
op_join.go		op_join.go
op_keys.go		op_keys.go
op_load.go		op_load.go
op_negate.go		op_negate.go
op_null.go		op_null.go
op_param.go		op_param.go
op_prune.go		op_prune.go
op_shuffle.go		op_shuffle.go
op_sort.go		op_sort.go
op_static_ips.go		op_static_ips.go
op_stringify.go		op_stringify.go
op_vault.go		op_vault.go
operator.go		operator.go
operator_test.go		operator_test.go
sort_test.go		sort_test.go
vault_test.go		vault_test.go

Name		Name	Last commit message	Last commit date
.github		.github
assets		assets
cmd/spruce		cmd/spruce
doc		doc
examples		examples
log		log
tests		tests
vendor		vendor
.gitignore		.gitignore
.travis.yml		.travis.yml
.whitesource		.whitesource
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
diff.go		diff.go
diff_test.go		diff_test.go
errors.go		errors.go
evaluator.go		evaluator.go
evaluator_test.go		evaluator_test.go
go.mod		go.mod
go.sum		go.sum
json.go		json.go
merge.go		merge.go
merge_test.go		merge_test.go
op_aws.go		op_aws.go
op_base64.go		op_base64.go
op_base64_decode.go		op_base64_decode.go
op_calc.go		op_calc.go
op_cartesian_product.go		op_cartesian_product.go
op_concat.go		op_concat.go
op_defer.go		op_defer.go
op_empty.go		op_empty.go
op_file.go		op_file.go
op_grab.go		op_grab.go
op_inject.go		op_inject.go
op_ips.go		op_ips.go
op_join.go		op_join.go
op_keys.go		op_keys.go
op_load.go		op_load.go
op_negate.go		op_negate.go
op_null.go		op_null.go
op_param.go		op_param.go
op_prune.go		op_prune.go
op_shuffle.go		op_shuffle.go
op_sort.go		op_sort.go
op_static_ips.go		op_static_ips.go
op_stringify.go		op_stringify.go
op_vault.go		op_vault.go
operator.go		operator.go
operator_test.go		operator_test.go
sort_test.go		sort_test.go
vault_test.go		vault_test.go

Name		Name	Last commit message	Last commit date
.github		.github
assets		assets
cmd/spruce		cmd/spruce
doc		doc
examples		examples
log		log
tests		tests
vendor		vendor
.gitignore		.gitignore
.travis.yml		.travis.yml
.whitesource		.whitesource
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
diff.go		diff.go
diff_test.go		diff_test.go
errors.go		errors.go
evaluator.go		evaluator.go
evaluator_test.go		evaluator_test.go
go.mod		go.mod
go.sum		go.sum
json.go		json.go
merge.go		merge.go
merge_test.go		merge_test.go
op_aws.go		op_aws.go
op_base64.go		op_base64.go
op_base64_decode.go		op_base64_decode.go
op_calc.go		op_calc.go
op_cartesian_product.go		op_cartesian_product.go
op_concat.go		op_concat.go
op_defer.go		op_defer.go
op_empty.go		op_empty.go
op_file.go		op_file.go
op_grab.go		op_grab.go
op_inject.go		op_inject.go
op_ips.go		op_ips.go
op_join.go		op_join.go
op_keys.go		op_keys.go
op_load.go		op_load.go
op_negate.go		op_negate.go
op_null.go		op_null.go
op_param.go		op_param.go
op_prune.go		op_prune.go
op_shuffle.go		op_shuffle.go
op_sort.go		op_sort.go
op_static_ips.go		op_static_ips.go
op_stringify.go		op_stringify.go
op_vault.go		op_vault.go
operator.go		operator.go
operator_test.go		operator_test.go
sort_test.go		sort_test.go
vault_test.go		vault_test.go

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Introducing Spruce

How do I get started?

How do I compile from source?

A Quick Example

Documentation

What else can Spruce do for you?

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Introducing Spruce

How do I get started?

How do I compile from source?

A Quick Example

Documentation

What else can Spruce do for you?

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Introducing Spruce

How do I get started?

How do I compile from source?

A Quick Example

Documentation

What else can Spruce do for you?

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Introducing Spruce

How do I get started?

How do I compile from source?

A Quick Example

Documentation

What else can Spruce do for you?

License

About

Resources