https://github.com/purecloudlabs/devcenter-blueprint-linter
A CLI tool for checking if a devcenter blueprint meets basic standards
https://github.com/purecloudlabs/devcenter-blueprint-linter
Last synced: 5 months ago
JSON representation
A CLI tool for checking if a devcenter blueprint meets basic standards
- Host: GitHub
- URL: https://github.com/purecloudlabs/devcenter-blueprint-linter
- Owner: purecloudlabs
- License: mit
- Created: 2022-03-30T12:46:44.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2025-01-03T06:34:23.000Z (over 1 year ago)
- Last Synced: 2025-04-04T20:36:21.316Z (over 1 year ago)
- Language: Go
- Size: 19.9 MB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# devcenter-blueprint-linter
A CLI tool for checking if a devcenter blueprint meets basic standards
The linter can check for remote or local repositories. The tool also supports Golang templates for customized output.
## Building the CLI
In the project root, run the command:
```bash
make build
```
This will build the binary `./bin/gc_linter` for the current OS.
## Running the Linter
To check all possible options, check the help option:
```bash
gc_linter -h
```
## Example Usage
```bash
gc_linter https://github.com/GenesysCloudBlueprints/automated-callback-blueprint -r -c ./blueprint.rule.json > result.json
```
## Logging
To enable logging, add the flag `-l` or `--enable-logging` to the command.
The log file should appear in the following directories depending on your OS:
Windows: `%TEMP%\GenesysCloud`
Unix: `/tmp/GenesysCloud`
OSX: `/Library/Logs/GenesysCloud`