native yaml configs & separate breeder naming #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: breeder create now requires --name parameter
Changes:
Usage:
godon_cli breeder create --name my-breeder --file config.yaml
Config file (config.yaml) now contains flat structure without name:
meta: configVersion: "0.2" breeder: type: "linux_performance" settings: {...} run: {...} cooperation: {...} objectives: [...] effectuation: {...}
The name is provided separately via CLI parameter and combined
with config when sending to API: {"name": "my-breeder", "config": {...}}