-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
392f241
commit 0804791
Showing
3 changed files
with
146 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,137 @@ | ||
# yamine [![Mean Bean CI](https://github.com/avencera/yamine/workflows/Mean%20Bean%20CI/badge.svg)](https://github.com/avencera/yamine/actions?query=workflow%3A%22Mean+Bean+CI%22) | ||
|
||
A simple CLI for combining json and yaml files | ||
|
||
## Install | ||
|
||
Available via Homebrew/Linuxbrew | ||
|
||
`brew install avencera/yamine/yamine` | ||
|
||
or | ||
|
||
Install from a github release: | ||
|
||
`curl -LSfs https://avencera.github.io/yamine/install.sh | sh -s -- --git avencera/yamine` | ||
|
||
or | ||
|
||
Download a release directly from github: [github.com/avencera/yamine/releases](https://github.com/avencera/yamine/releases) | ||
|
||
## Usage | ||
|
||
`yamine --help` | ||
|
||
``` | ||
Combine JSON/YAML files into a single YAML file | ||
USAGE: | ||
yamine [FLAGS] [OPTIONS] <FILES_OR_FOLDERS>... | ||
FLAGS: | ||
--dry-run Default mode | ||
-h, --help Prints help information | ||
-s, --std-out Outputs combined file contents to STDOUT | ||
-V, --version Prints version information | ||
-w, --write Write new output file | ||
OPTIONS: | ||
-d, --depth <depth> Number of folder depth to recurse into [default: 1] | ||
-f, --format <format> The format for the output file, defaults to yaml, options are: 'yaml', 'json', 'k8s-json' | ||
[default: yaml] | ||
-o, --output <output> Output file name [default: combined.yaml] | ||
ARGS: | ||
<FILES_OR_FOLDERS>... File(s) or folder you want to run in | ||
``` | ||
|
||
### Examples | ||
|
||
- Combine all yaml and json files in the current folder and creates `combined.yaml` file | ||
- `yamine -w .` | ||
- Combine all yaml and json files in the current folder and creates a `combined.json` file in `json-k8s` format: | ||
- `yamine --write --format json-k8s --output combined.json .` | ||
- Output the combined file to STDOUT in json-array format: | ||
- `yamine --std-out -f json-array .` | ||
|
||
### Formats | ||
|
||
- `yaml` - a multi document yaml file separated by `---` (a kubernetes multi resource document) | ||
|
||
```yaml | ||
--- | ||
apiVersion: traefik.containo.us/v1alpha1 | ||
kind: IngressRoute | ||
--- | ||
apiVersion: v1 | ||
kind: Namespace | ||
metadata: | ||
name: example | ||
--- | ||
kind: ServiceAccount | ||
apiVersion: v1 | ||
--- | ||
apiVersion: v1 | ||
kind: Service | ||
--- | ||
apiVersion: apps/v1 | ||
kind: Deployment | ||
``` | ||
- `json-array` - a json file with each combined file being an element in the array | ||
|
||
```json | ||
[ | ||
{ | ||
"apiVersion": "traefik.containo.us/v1alpha1", | ||
"kind": "IngressRoute" | ||
... | ||
}, | ||
{ | ||
"apiVersion": "v1", | ||
"kind": "Namespace", | ||
... | ||
}, | ||
{ | ||
"apiVersion": "v1", | ||
"kind": "ServiceAccount", | ||
... | ||
}, | ||
{ | ||
"apiVersion": "v1", | ||
"kind": "Service", | ||
... | ||
}, | ||
] | ||
``` | ||
|
||
- `json-k8s` - a kubernetes multi resource json document ex: | ||
|
||
```json | ||
{ | ||
"kind": "List", | ||
"apiVersion": "v1", | ||
"items": [ | ||
{ | ||
"apiVersion": "traefik.containo.us/v1alpha1", | ||
"kind": "IngressRoute" | ||
... | ||
}, | ||
{ | ||
"apiVersion": "v1", | ||
"kind": "Namespace", | ||
... | ||
}, | ||
{ | ||
"apiVersion": "v1", | ||
"kind": "ServiceAccount", | ||
... | ||
}, | ||
{ | ||
"apiVersion": "v1", | ||
"kind": "Service", | ||
... | ||
}, | ||
] | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters