- Added LWP::Protocol::https so the client support HTTPS
- The
NO_COLOR
environment variable is now supported. It might have been via Term::ANSIColor, but now it is documented and explicitly implemented
- Colors for output can now be customized using environment variables
- Colors for output can now be customized using the configuration file
0.18.0 2020-12-26 Milestone release, implemented handling of URLs for checksum resources and checksum calculation
-
The feature of fetching a checksums resource via URL added
-
The feature of fetching a single checksum resource via URL for dynamic calculation added
-
Added use of LWP::UserAgent as a dependency
-
The feature of reporting on required files not being found has now been implemented
-
Added use of Clone as a dependency
- Stabilizing implementation with several bug fixes found by manual testing, particularly in the configuration handling
-
Rolled into Dist::Zilla based release
-
Added
--version
command line argument
- Improved the handling of the configuration and data file handling
- Added support for checking file presence
- in the data source (checksums file) you can now specify a boolean instead of a checksum or file
true
meaning thatyak
succeeds if the file is present and fails if notfalse
meaning thatyak
succeeds if the file is not present and fails if it is
0.12.0 2020-12-04 Milestone release, implementing support for .yakignore
and configuration of file ignores
- Added support for ignoring files
- adding local
.yakignores
for deep directory trees - added patterns to configuration under
ignore_dirs:
- the
.yakignores
andignore_dirs
is based on an.gitignore
implementation
- adding local
--about
now outputs the values of relevant environment variables- outputs value of
$CLICOLOR
if defined - outputs value of
$CLICOLOR_FORCE
if defined
- outputs value of
0.10.0 2020-11-25 Milestone release, implementing support for controlling colorized output using environment
- Added support for environment variable
$CLICOLOR
- overrides config can be overridden by command line flags
- Added support for environment variable
$CLICOLOR_FORCE
- overrides config,
$CLICOLOR
and command line flags
- overrides config,
-
Added configuration option
success_emoji
- can be configured in:
$HOME/.config/yak/config.yaml
- can be used to override default emoji for successful checks
- can be configured in:
-
Added configuration option
failure_emoji
- can be configured in:
$HOME/.config/yak/config.yaml
- can be used to override default emoji for failing checks
- can be configured in:
-
Added configuration option
skip_emoji
- can be configured in:
$HOME/.config/yak/config.yaml
- can be used to override default emoji for skipped checks
- can be configured in:
-
Added configuration option
emoji
- can be configured in:
$HOME/.config/yak/config.yaml
- can be used to override default value of enabled
- can be configured in:
-
Added command line argument
--emoji
- can be used to override
emoji
configuration specified in:$HOME/.config/yak/config.yaml
- can be used to override
-
Added command line argument
--noemoji
- overriding default value of enabled
- can be used to override
emoji
configuration specified in:$HOME/.config/yak/config.yaml
- overriding
--emoji
command line argument
-
Added configuration option
color
- can be configured in:
$HOME/.config/yak/config.yaml
- can be used to override default value of enabled
- can be configured in:
-
Added command line argument
--color
- can be used to override
color
configuration specified in:$HOME/.config/yak/config.yaml
- can be used to override
-
Added command line argument
--nocolor
- overriding default value of enabled
- can be used to override
color
configuration specified in:$HOME/.config/yak/config.yaml
- overriding
--color
command line argument
- Added command line argument
--config <data source file>
- using specified data source file instead of the default:
$HOME/.config/yak/checksums.json
- fixed a minor bug introduced in mile stone release 0.5.0 where
--about
would emit nonsense
- using specified data source file instead of the default:
- Added command line argument
--config <configuration file>
- using specified configuration file instead of the default:
$HOME/.config/yak/config.yaml
- using specified configuration file instead of the default:
- Added command line argument
--help
and it emits:- listing of all command line options with short description
- Added command line argument
--about
and it emits: - current version number of
yak
- configuration file location/path
- data source (file) location/path
- invocation command line arguments, including
--about
- invocation environment (meaning the sum of configuration and invocation), currently just the configuration file contents, not the sum
yak
can now be build as a Docker container- Added command line arguments are:
--noconfig
disables reading of$HOME/.config/yak/config.yml
so invocation relies solely on command line arguments--nochecksums
disables reading of$HOME/.config/yak/checksums.yml
so checksum data has to be read from the directory in whichyak
is executed and it has to be names.yaksums.json
,
- The command line arguments:
--noconfig
and--nochecksums
are mandatory for the Docker entrypoint
- Can be configured using file and configuration supports:
verbosity
tellsyak
to emit more verbose outputdebug
tellsyak
to emit debug output- the configuration file is in YAML and has to be placed in:
$HOME/.config/yak/config.yml
- Can take command line arguments, currently supported is
--verbose
overwrites config and tellsyak
to emit more verbose output--debug
overwrites config and tellsyak
to emit debug output--silent
silencesyak
and you have to rely on the return value--nodebug
tellsyak
not to output debug no matter configuration or commandline flag--debug
(see above)
- Persistent data for
yak
is supported- data has to be written to a JSON file placed in:
$HOME/.config/yak/checksums.json
- data has to be written to a JSON file placed in: