fsoc solution validate

Validate solution

Synopsis

This command allows the current tenant specified in the profile to upload the solution in the current directory just to validate its contents. The --stable flag provides a default value of 'stable' for the tag associated with the given solution. 

fsoc solution validate [flags]

Examples

  fsoc solution validate
  fsoc solution validate --bump --tag preprod
  fsoc solution validate --tag dev
  fsoc solution validate --stable
  fsoc solution validate -d mysolution --tag dev
  fsoc solution validate --solution-bundle=mysolution-1.22.3.zip --tag stable

Options

  -b, --bump                     Increment the patch version before validation
  -d, --directory string         Path to the solution root directory (defaults to current dir)
      --env-file string          Path to the env vars json file with pseudo-isolation tag and, optionally, dependency tags (DEPRECATED)
  -h, --help                     help for validate
      --no-isolate               Disable fsoc-supported solution pseudo-isolation
      --solution-bundle string   Path to a prepackaged solution zip
      --stable                   Use the stable tag for solution isolation. Equivalent to --tag=stable
      --tag string               Tag to use for solution isolation

Options Inherited From Parent Commands

      --config string      config file (default is ~/.fsoc). May be .yaml or .json
      --curl               log curl equivalent for platform API calls (implies --verbose)
      --fields string      perform specified fields transform/extract JQ expression
      --log string         set a location and name for the fsoc log file (default "/tmp/fsoc.log")
      --no-version-check   skip the daily check for new versions of fsoc
  -o, --output string      output format (auto, table, detail, json, yaml) (default "auto")
      --profile string     access profile (default is current or "default")
  -v, --verbose            enable detailed output

See Also