maa-import(1)

πŸ“¦
version 0.7.7 Β· 2 versions
, in nixpkgs unstable

okay so welcome to maa-import(1), General Commands Manual β€” the page for maa-import, the command that imports configuration files from a local path or a remote URL. bestie, this is literally your config-importing main character, and we’re going through every flag with zero skips. πŸ’…βœ¨

πŸŽ€ NAME πŸŽ€

maa-import β€” import configuration files from a local path or a remote URL.

✨ SYNOPSIS ✨

maa import [-n|--name] [-f|--force] [-t|--config-type] [--batch]
[-v|--verbose]... [-q|--quiet]... [--log-file] [-h|--help] <SRC>

πŸ’– DESCRIPTION πŸ’–

Import configuration files from a local path or a remote URL.

okay so this command is your little doorway for importing lots of different configuration file types into the maa-cli config directory. lowkey iconic: you can use it to add new tasks, profiles, and other configurations. 🫢

🌈 OPTIONS 🌈

  • -n, --name <NAME> β€” the desired name for the imported configuration file.

if you don’t specify it, the filename gets derived from the source path or URL. this is especially useful when you’re importing from a URL that doesn’t have a clear filename. ✨

  • -f, --force β€” force the import operation even if a file with the same name already exists.

for CLI-read configurations, this also applies to files with the same stem but a different extension. no cap, stem rules included.

  • -t, --config-type <CONFIG_TYPE> [default: task] β€” the category of the configuration file, which determines its storage location and validation rules.

possible values:

  • cli β€” CLI configuration file
  • profile β€” Assistant/Profile configuration
  • task β€” Task configuration
  • infrast β€” Infrastructure configuration
  • resource β€” Resource configuration
  • copilot β€” Copilot configuration
  • sss-copilot β€” SSSCopilot configuration
  • paradox-copilot β€” ParadoxCopilot configuration
  • --batch β€” enable batch mode.

if there are some input parameters in the task file, some prompts will be displayed to ask for input. in batch mode, the prompts will be skipped, and parameters will be set to default values. very β€œhandle it without me” energy. πŸ’…

  • -v, --verbose β€” increase verbosity, repeat for more verbosity.
  • -q, --quiet β€” decrease verbosity, repeat for more quiet.
  • --log-file[=<PATH>] β€” redirect log to file instead of stderr.

if no log file is specified, the log will be written to $(maa dir log)/YYYY/MM/DD/HH:MM:SS.log. πŸ—‚οΈ

  • -h, --help β€” print help (see a summary with -h).
  • <SRC> β€” the source of the configuration file to be imported.

this can be a local file path or a remote HTTP(S) URL.

🚨 bestie, when importing from a URL, be sure to only use trusted sources. the file will be downloaded and placed in your configuration directory. please don’t let random links into the group chat.

if you are importing from a URL that does not have a clear filename in the path (e.g., a URL with query parameters), you should use the --name option to specify a filename for the imported configuration.

when importing a local file that is a symbolic link, the contents of the target file will be copied, not the link itself. yes, the target’s vibe, not the link’s vibe. πŸ¦‹


cute sign-off bestie: source/version import, manual maa-import(1), and the footer date slot all get folded into this little sign-off instead of a raw copied line. bye, go import your configs safely! πŸ’œπŸŒΈ

πŸ“¦ where this page comes from