Upsert will create a new suite in APId cloudcontaining all the transactions defined in
apid.yaml in the current directory. If a suite with the specified name exists it will replace it instead.
It can optionally take a path to the config via the
--config flag. To get familiar with the syntax of a config file, see here
Suites in APId cloud use the same syntax as the locally ran configs, thus it is really easy to upload your existing tests with one command. The only difference is that you'll need to provide a couple of extra top level values -
schedule and a list of
locations. These are needed so APId knows when and where to execute your suite. You can learn more about these in the config Reference section.
The name of the suite, used to later reference it (enable, replace)
Your API key, this can also be injected via the
The config file. If a folder is provided will recursively load all
apid cloud suite upsert -c ./tests/e2e/apid.yaml -n simple-suite -k <apid cloud key>