fcli tool: Add fcli tool * install --base-dir option to specify the base directory under which all tools will be installed. By default, fcli will now also install tool invocation scripts in a global <base-dir>/bin directory, unless the --no-global-bin option is specified. This allows for having a single bin-directory on the PATH, while managing the actual tool versions being invoked through the fcli tool * install commands. (e2db51d)
fcli tool: Add fcli tool * install --uninstall option to remove existing tool installations while installing a new tool version, allowing for easy tool upgrades. (e2db51d)
fcli tool: Add fcli tool debricked-cli commands for installing Debricked CLI and managing those installations. (e2db51d)
fcli tool: Add fcli tool definitions commands, allowing tool definitions to be updated to make fcli aware of new tool versions that were released after the current fcli release. Customers may also host customized tool definitions, for example allowing for alternative tool download URLs or restricting the set of tool versions available to end users. (e2db51d)
fcli tool: Add fcli tool fcli commands for installing Fortify CLI and managing those installations. (e2db51d)
fcli tool: By default, the fcli tool * install commands will now install tools under the <user.home>/fortify/tools base directory (no dot/hidden directory), instead of <user.home>/.fortify/tools (e2db51d)
fcli tool: Deprecate fcli tool * install --install-dir option; the new --base-dir option is now preferred as it supports new functionality like global bin-scripts. (e2db51d)
Bug Fixes
fcli ssc: The --attributes option on fcli ssc appversion * and fcli ssc attribute * commands now supports setting multiple values for an attribute (bd3fd62)
:robot: I have created a release beep boop
2.2.0 (2024-02-05)
Features
fcli fod
: Addfcli fod report
commands for creating and downloading FoD reports (resolves #263) (5796379)fcli fod
: Add preview commands for starting and managing DAST Automated scans (db898ee)fcli ssc
: Addfcli ssc report
commands for generating, downloading & managing SSC reports (resolves #205) (60e7855)fcli tool
: Addfcli tool * install --base-dir
option to specify the base directory under which all tools will be installed. By default, fcli will now also install tool invocation scripts in a global<base-dir>/bin
directory, unless the--no-global-bin
option is specified. This allows for having a single bin-directory on thePATH
, while managing the actual tool versions being invoked through thefcli tool * install
commands. (e2db51d)fcli tool
: Addfcli tool * install --uninstall
option to remove existing tool installations while installing a new tool version, allowing for easy tool upgrades. (e2db51d)fcli tool
: Addfcli tool debricked-cli
commands for installing Debricked CLI and managing those installations. (e2db51d)fcli tool
: Addfcli tool definitions
commands, allowing tool definitions to be updated to make fcli aware of new tool versions that were released after the current fcli release. Customers may also host customized tool definitions, for example allowing for alternative tool download URLs or restricting the set of tool versions available to end users. (e2db51d)fcli tool
: Addfcli tool fcli
commands for installing Fortify CLI and managing those installations. (e2db51d)fcli tool
: By default, thefcli tool * install
commands will now install tools under the<user.home>/fortify/tools
base directory (no dot/hidden directory), instead of<user.home>/.fortify/tools
(e2db51d)fcli tool
: Deprecatefcli tool * install --install-dir
option; the new--base-dir
option is now preferred as it supports new functionality like global bin-scripts. (e2db51d)Bug Fixes
fcli ssc
: The--attributes
option onfcli ssc appversion *
andfcli ssc attribute *
commands now supports setting multiple values for an attribute (bd3fd62)This PR was generated with Release Please. See documentation.