Uploaded image for project: 'stripes-cli'
  1. stripes-cli
  2. STCLI-117

Support okapi/tenant values from stripes.config.js for okapi-based commands

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.9.0
    • Labels:
      None
    • Template:

      Description

      Currently the build/serve/test commands make use of the okapi URL and tenant ids in a tenant config (stripes.config.js). This is because the tenant config is a dependency on the build process. Optionally the CLI allows the okapi URL and tenant id to be specified on the command line via --okapi and --tenant, effectively overriding values in the tenant config.

      These --okapi and --tenant options exist because several other CLI commands require them for interacting with Okapi, but don't otherwise require a full tenant config. However, some new okapi-based commands, like stripes platform backend, also consume the tenant config, yet the CLI does not know to that they could be obtained from here. This captures the work needed to parse okapi URL and tenant id from the tenant config for these okapi-based commands.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                mattj Matt Jones
                Reporter:
                mattj Matt Jones
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases