Phil Henning

Also I knew absolutely no GoLang this morning, so critique away wise ones

Yea it's tough. I don't know if the CLI tool really fits in the image. I'm trying to think of a reason I'd want to create an operations repo within...

In addition to this we should move the defaults for these config values into the schema and out of the core.

## These look like strong choices; # config-lint https://stelligent.github.io/config-lint/#/?id=config-lint https://github.com/stelligent/config-lint ## Pros 1. It's highly customizable 1. It can be used to validate configuration files that use; Yaml, JSON, Terraform...

# Update ## Polaris The Polaris validator requires a schema for each config we wish to validate. The issue is that, we'd be making schemas for schemas, and that would...

Sure - # State of today The lookup function has been added A single lookup message has been added in the docs.json # State of tomorrow - Consolidate all error...

It wouldn't be duplication. We'd take advantage of a centralized file to keep logging messages in. Keeping them generic means that they can be used in more then one way.

Should I update the name of this [page](https://github.com/bitovi/bitops/blob/plugins/docs/migration/2.0.0-migration.md) to `2.0.0-CHANGELOG.md` ??

# Option 1 - Configuration saved in Bitops/bitops.config.yaml # Option 2 - Configuration saved in OpsRepo/ENV/PLUGIN/bitops.config.yaml

**bitops/bitops.config.yaml** - Add `default folder` configuration - Add Sub-directory configuration - would be built by Bitops Core and would look like the following; `opsrepo//` **Helm** - Add `subdirectory` default flag...