context

qlik context

Create, update and use contexts

Synopsis

Create, update and use contexts

Contexts store connection information such as server url, certificates and headers, similar to a config. The main difference between contexts and configs is that they can be used globally. Use the context subcommands to configure contexts which facilitate app development in environments where certificates and headers are needed.

The current context is the one that is being used. You can use “context get” to display the contents of the current context and switch context with “context use” or unset the current context with “context clear”.

Note that contexts have the lowest precedence. This means that e.g. an —server flag (or a server field in a config) will override the server url in the current context.

Contexts are stored locally in your ~/.qlik/contexts.yml file.

qlik context [flags]

Options

  -h, --help   help for context

Options inherited from parent commands

  -c, --config string            path/to/config.yml where parameters can be set instead of on the command line
      --context string           Name of the context used when connecting to Qlik Associative Engine
      --headers stringToString   HTTP headers to use when connecting to Qlik Associative Engine (default [])
      --insecure                 Enabling insecure will make it possible to connect using self-signed certificates
      --json                     Returns output in JSON format, if possible. Disables verbose and traffic output
  -s, --server string            URL to Qlik Cloud or directly to a Qlik Associative Engine
      --server-type string       The type of server you are using: cloud, Windows (Enterprise on Windows) or engine
  -v, --verbose                  Log extra information