StormForge CLI
StormForge CLI release history
Version 6.0.2
Changed
- Dependency updates
- Changed the version columns shown by
get clusters
Fixed
- Corrected the URL emitted by the
check versioncommand - The patch command no longer ignores the target subresource
Version 6.0.1
Added
- Restored the v5
edit cluster --reset-uidoption - Restored the v5
--recommendationoption for specifying recommendation names
Changed
- Dependency updates
Removed
- The macOS binaries are no longer notarized
Fixed
- Fixed an issue where get recommendations got too many results in YAML output
- Fixed an issue where the edit command would not report bad patch errors
Version 6.0.0
Added
- There is a new
stormforge viewcommand for fetching output comparable to the web UI - There is a new
stormforge describecommand for fetching a more detailed view of a resource - There is a new
stormforge managecommand for manually configuring resources
Changed
- Commands accept a slash delimited name argument instead of (or in addition to) the filtering flags
- The
stormforge getcommand shows different fields - The
stormforge editcommand now launches an interactive editor
Removed
- Optimize Pro functionality has been removed
- Performance Test functionality has been removed
Fixed
- The
--selectorargument is not ignored for tab completions - Some commands mistakenly bypassed filtering requirements
- Flag and argument completions are more consistent
Version 5.1.13
Fixed
- Fixes an issue where
-o namewas selected when a TTY isn’t available
Version 5.1.12
Changed
- Dependency updates
Version 5.1.11
Changed
- Dependency updates
Fixed
- Fix for empty values showing up as “”
Version 5.1.10
Changed
- Dependency updates
- The Go Template output has improved support for Kubernetes quantities
- Recommendation output includes JVM max heap (if applicable)
Version 5.1.9
Changed
- Dependency updates
Fixed
- The workload patches can be read from stdin
Version 5.1.8
Changed
- Dependency upgrades
- Fixed an issue where some authorization scopes were not being requested
Version 5.1.7
Changed
- Dependency updates
Fixed
- Fixes an issue where the
stormforge auth listresults could be truncated
Version 5.1.6
Changed
- Dependency upgrades
Version 5.1.5
Changed
- Dependency upgrades
Security
- Built using Go 1.22.3 to address CVE-2024-24788
Version 5.1.4
Changed
- Added missing workload impact data to the
stormforge get workloadoutput
Version 5.1.3
Added
- When creating auto-deployed recommendations, you can now include a
--waitflag and corresponding--timeoutflag to delay applying the recommendation
Changed
- Workload CSV numeric values are rendered at a fixed precision
Fixed
- The
stormforge applycommand now correctly reapplies recommendations - Sort keys are not silently ignored
Version 5.1.2
Added
- The
getcommands now support limited client-side filtering using Kubernetes field selectors via the--field-selectoroption - The
get workloadscommand now has a--full-fetchoption to force fetching all data from the API (note: this might take extra time to run)
Fixed
- The CSV columns named
auto-deployandhpa-enabledare now namedauto_deployandhpa_enabled - The
get workloadscommand now shows “UNAVAILABLE” for values that were not fetched from the API
Version 5.1.1
Changed
- Added
schedule,auto-deploy, andhpa-enabledcolumns to the workload CSV output
Security
- Updated go-jose to address CVE-2024-28180
Version 5.1.0
Changed
- Optimize Pro commands are now hidden
- The
stormforge patchcommand supports multiple recommendations - Workload CSV output includes
replicasandoptimization_score
Removed
- The
stormforge runcommand has been removed - The
stormforge edit workload labelcommand has been removed. Usestormforge edit workload --set-labelinstead.
Fixed
- The
Deletedvalue is no longer suggested for--stateflags - Create recommendation failures are properly reported
- Allow recommendations to be sorted by timestamp
- The
applycommand now prevents empty filters
Security
- Switched container image base from Alpine to Distroless
Version 5.0.6
Added
- The new
stormforge edit clustercommand can be used to manage cluster resources
Changed
- The
stormforge applycommand no longer applies recommendations that have insufficient data unless--forceis used
Deprecated
- The
stormforge edit workload labelcommand is now deprecated. Usestormforge edit workload --set-labelinstead. - Deprecation notice: Starting in the next release, in an effort to reduce dependencies, the
stormforge-clicontainer image will no longer include a shell.
Fixed
- The
stormforge get workloadtable view honors--show-impact - The
stormforge get recommendationscommand now fetches all recommendations correctly when you specify JSON, YAML, or CSV output format
Security
- Upgrades dependencies with known vulnerabilities
Version 5.0.5
Changed
- Dependency upgrades
Fixed
- JSON and YAML output should have matching field ordering
Version 5.0.4
Changed
- The
edit workload handlers --auto-deployflag is no longer implied by the thresholds - The
edit workload container-resourcescommand accepts theRequestsAndLimitspolicy
Fixed
- The
edit workload container-resourcescommand can unset values
Version 5.0.3
Added
- Support for workload auto-deploy thresholds. See the
stormforge edit workload handlerscommand in the CLI reference. - Workloads can be filtered by over- or under-provisioned state
Changed
- Removed references to workload schedule names
Fixed
- The
auth revokecommand was not accepting client identifiers
Version 5.0.2
Changed
- The
get clusteroutput now includes the Optimize Live and StormForge Applier version numbers
Fixed
- The
check connectworks correctly when testing client credentials - Generating tokens no longer requests the
offline_accessscope
Version 5.0.1
Changed
- Updated recommendation state names
Fixed
- The authorization issuer was not configured properly in some cases
Version 5.0.0
Changed
- Workload and recommendation commands reflect consolidation to a single schedule
- The
stormforge get workloadscommand hides impact details unless--show-impactis used
Removed
- The
installanduninstallcommands have been removed
Fixed
- The
stormforge edit workloadcommands ignore workloads using in-cluster configuration