coconut_configuration_import.md

coconut configuration import

Import a configuration file for the specified component and entry

Synopsis

The configuration import command generates a timestamp and saves the configuration file to Consul under the / path. Supported configuration file types are JSON, YAML, TOML and INI, and their file extensions are recognized automatically.

coconut configuration import <component> <entry> <file_path> [flags]

Examples

coconut conf import <component> <entry> <file_path>
coconut conf import <component>/<run type>/<machine role>/<entry> <file_path>
coconut conf import <component> <entry> <file_path> --new-component
coconut conf import <component>/<run type>/<machine role>/<entry> <file_path> --format=json
coconut conf import <component> <entry> <file_path>.json
coconut conf import <component> <entry> <file_path> 
coconut conf import <component> <entry> <file_path> --new-component

Options

  -f, --format string    force a specific configuration file type, overriding any file extension
  -h, --help             help for import
  -n, --new-component    create a new configuration component while importing entry
  -l, --role string      request configuration for this O² machine role
  -r, --runtype string   request configuration for this run type (e.g. PHYSICS, TECHNICAL, etc.)

Options inherited from parent commands

      --config string            optional configuration file for coconut (default $HOME/.config/coconut/settings.yaml)
      --config_endpoint string   configuration endpoint used by AliECS core as PROTO://HOST:PORT (default "apricot://127.0.0.1:32101")
      --endpoint string          AliECS core endpoint as HOST:PORT (default "127.0.0.1:32102")
      --nocolor                  disable colors in output
      --nospinner                disable animations in output
  -v, --verbose                  show verbose output for debug purposes

SEE ALSO

• coconut configuration - view or modify O² configuration

Auto generated by spf13/cobra on 27-Nov-2024