Create Boilerplate integration commands

staticaland commented 2 weeks ago

### Tasks
- [x] Phase out `ok get` command
- [x] Create `ok pkg install` command
- [ ] Phase out `get-template` and `get` subcommands

Undecided

What to name the package file?
- package.yml
- Platefile.yml
- .boilerplate.yml

Could it be useful to include Boilerplate in the name?

Consider	Decision	Why
Move vars to configuration (`package.yml`) file	🟥	Can't be used with regular Boilerplate CLI
Use JSON	🟥	Boilerplate uses YAML
Use YAML	💚	Same as Boilerplate, i.e. give users same UX for Boilerplate and `ok`. Not included in Go standard library.
Use `go-yaml/yaml`	💚	Decent library. Not updated in 2 years. Easy to replace if needed.
Use same variable names as Boilerplate and Git (`ref`)	💚	No better suggestions
Use pascal case in config	💚	Boilerplate uses pascal case because it's a Go convention. However, snake case is arguably easier to read. Search the web for the science. However, we choose to use same convention for both `Boilerplate` and `ok` (i.e. pascal case). Consider changing both to snake case.
Add this feature to Boilerplate itself	🟥	Too many unknowns

template_url: app
ref: v1.0.0
output_folder: app-km
var_files:
  - file1.yml
  - file2.yml

templateUrl: app
ref: v1.0.0
outputFolder: app-km
varFiles:
  - file1.yml
  - file2.yml

TemplateUrl: app
Ref: v1.0.0
OutputFolder: app-km
VarFiles:
  - file1.yml
  - file2.yml

staticaland commented 1 week ago

staticaland commented 6 days ago