diff --git a/documentation/guides/automation/cli/index.html b/documentation/guides/automation/cli/index.html index 8fc2d437..3ec550aa 100644 --- a/documentation/guides/automation/cli/index.html +++ b/documentation/guides/automation/cli/index.html @@ -44,7 +44,7 @@ --keycloakClientSecret=ab54d329-e435-41ae-a900-ec6b3fe15c54 \ --operationsHeaders='{"globals": [{"name": "x-api-key", "values": "azertyuiop"}], "GET /pastries": [{"name": "x-trace-id", "values": "qsdfghjklm"}]}' \ --insecure --waitFor=6sec -

Check the microcks-cli README for full instructions on arguments and flags.

Wrap-up

You have learned how to install and use the Microcks CLI for the basic task of launching a new test. This is waht you would typically do within your CI/CD pipeline to ensure the application you just deployed correctly implements API specifications.

Microcks CLI also provide the import command that allows you to push artifacts into Microcks repository. This command requires that you have a Service Account with more privileges than the default one though. You may follow-up this guide with learning more about Service Accounts.

The CLI provides the helpful commands version and help to get basic informations on it. Check the microcks-cli README for full instructions on available commands depending your version.