v0.42.0

What's Changed

• Added support for --tag to solution subscribe/unsubscribe commands, to support working with dev solutions (not stable)
• Improved usage help for solution and knowledge commands

Full Changelog: v0.41.0...v0.42.0

v0.41.0

• Config file and profile name can be specified in env vars FSOC_CONFIG and FSOC_PROFILE
• solution test command now works with the correct API endpoint (fsomon-test-runner)
• solution test-status now adds a Status field
• minor fixes:
  • solution bump, extend, isolate, package no longer enforce fsoc config file/auth
  • solution isolate is deprecated (use push or validate directly; or just package if you want to see the output)

v0.40.0

• The solution package command is back and better than before. It still produces zip files. It's intended to be used primarily in workflows for production release of solutions (most others should use push or validate directly using the solution directory).
• The solution validate and solution push commands again support taking ready zip files using the --solution-bundle flag (again, mostly targeting release workflows).
• The solution package, push and validate commands can now work with solutions not in the current working directory. The -d|--directory flag has the magic power🧙.
• Solution pseudo-isolation is now supported in the normal workflow commands: solution push, solution package and solution validate. If your solution has its name with ${} variable in it, it will automatically be isolated with the tag. fsoc supports 5 (five!) ways to specify tags, to support different use cases: --tag=<tag> flag, --stable flag (means --tag=stable), FSOC_SOLUTION_TAG env var, --env-file=<env-vars.json> flag and, the default: env.json file in the solution root directory (next to the manifest).

v0.39.0

What's Changed

• Added support for exporting boolean values in melt push
• Added tooling for interim solution isolation (hidden command, use fsoc help solution isolate for details)

New Contributors

• @k-shaikh made their first contribution in #104

Full Changelog: v0.38.0...v0.39.0

v0.38.0

What's Changed

• Added support for testing solutions (solution test and solution test-status)
• Added support for DashUI features and FMM associations in the solution extend command
• Extended optimize configure to use the SLO and guardrails data from the profiler as default values for optimization
• Moved zip files created as part of solution commands to the system temp folder

New Contributors

• @ddanuj made their first contribution in #86

Full Changelog: v0.37.0...v0.38.0

v0.37.0

What's Changed

• Added --tag flag to the solution download command (ORION-1225)
• Added commands for optimizer control: start, stop, suspend, unsuspend

Full Changelog: v0.36.0...v0.37.0

v0.36.0

What's Changed

• Added optimize configure command to set up goals and start optimizing workloads
• FSOC-134: clarify the syntax for the --type flag in knowledge commands

Full Changelog: v0.35.0...v0.36.0

v0.35.0

Add support for --tag and --stable flags in solution validate and solution push; remove default tag being stable to reduce chances of unintended push to production.

v0.34.1

What's Changed

• Fix EOF error for fsoc solution check --all command for solutions with components

New Contributors

• @cnadiminti made their first contribution in #90

Full Changelog: v0.34.0...v0.34.1

v0.34.0

What's Changed

• Added support for JSON Patch (rfc6902) and JSON Merge Patch (rfc7386) (see fsoc knowledge create-patch --help)
• Added optimize status command
• Improved solution status output to include subscription status (FSOC-140)
• Fixed output failures on null/empty results in optimize report command
• ORION-1115: add support for providing tag to solution push/validate (preliminary work to enable internal testing; do not use)

Full Changelog: v0.33.1...v0.34.0