You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2019. It is now read-only.
Reading through the help strings produced by MIG running in Docker, I came across some typos and inconsistencies that are practically inconsequential. I wanted to open an issue for them so that I might be able to address them as I familiarize myself with the codebase.
In the main mig --help output, there is a typo in "config"
-c path to an alternative confiig file. If not set, use ~/.migrc
Specifically,
confiig
The examples showing how to use the -t flag are a bit inconsistent (perhaps intentionally?)
-t target to launch the action on. A target must be specified.
examples:
* linux agents: -t "queueloc LIKE 'linux.%'"
* agents named mysql: -t "name like '%mysql%'"
Here, the second example has LIKE in lowercase.
In the description of the -size flag accepted by the file module
-size - match files with a size smaller or greater that
Specifically,
greater that
In the description of the -macroal flag accepted by the file module
-macroal - by default, a 'content' regex only need to match one line of a file
to return a match. With the 'macroal' option set, all line of a file
Specifically,
all line
The text was updated successfully, but these errors were encountered:
Reading through the help strings produced by MIG running in Docker, I came across some typos and inconsistencies that are practically inconsequential. I wanted to open an issue for them so that I might be able to address them as I familiarize myself with the codebase.
mig --help
output, there is a typo in "config"Specifically,
-t
flag are a bit inconsistent (perhaps intentionally?)Here, the second example has
LIKE
in lowercase.-size
flag accepted by thefile
moduleSpecifically,
-macroal
flag accepted by thefile
moduleSpecifically,
The text was updated successfully, but these errors were encountered: