You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*`--waitFor` for the time to wait for test to finish (int + one of: milli, sec, min),
75
-
*`--keycloakClientId` for the Keycloak Realm Service Account ClientId,
76
-
*`--keycloakClientSecret` for the Keycloak Realm Service Account ClientSecret.
77
-
78
-
> Since `0.5.2` release, `microcks-cli` also works in unauthenticated mode, without Keycloak being deployed and configured with your Microcks instance. However, you still have to specify the Keycloak flags on the command even if you put random values there. For eg. `--keycloakClientId=foo --keycloakClientSecret=bar`.
MicrocksClient got status fortest"5c1781cf6310d94f8169384e" - success: false, inProgress: true
90
-
MicrocksTester waiting for 2 seconds before checking again.
91
-
MicrocksClient got status fortest"5c1781cf6310d94f8169384e" - success: true, inProgress: false
92
-
Full TestResult details are available here: http://localhost:8080/#/tests/5c1781cf6310d94f8169384e
46
+
### Usage
47
+
```bash
48
+
microcks [command] [flags]
93
49
```
94
50
95
-
#### Advanced options
96
-
97
-
The `test` command provides additional flags for advanced usages and options:
98
-
99
-
*`--verbose` allows to dump on standard output all the HTTP requests and responses,
100
-
*`--insecure` allows to interact with Microcks and Keycloak instances through HTTPS without checking certificates issuer CA,
101
-
*`--caCerts=<path1,path2>` allows to specify additional certificates CRT files to add to trusted roots ones,
102
-
*`--secretName='<Secret Name>'` is an optional flag specifying the name of a Secret to use for connecting endpoint,
103
-
*`--filteredOperations=<JSON>` allows to filter a list of operations to launch a test for,
104
-
*`--operationsHeaders=<JSON>` allows to override some operations headers for the tests to launch,
105
-
*`--oAuth2Context=<JSON>` allows specification of an OAuth2 grant flow to execute before launching the test (starts with Microcks version `1.8.0`).
|`--caCerts`| Comma-separated paths of CA cert files |
74
+
|`--keycloakClientId`| Keycloak Realm Service Account ClientId |
75
+
|`--keycloakClientSecret`| Keycloak Realm Service Account ClientSecret |
76
+
|`--microcksURL`| Microcks API URL |
106
77
107
-
Overriden test operations headers is a JSON strings where 1st level keys are operation name (eg. `GET /beer`) or `globals` for header applying to all the operations of the API. Headers are specified as an array of objects defining `key` and `values` properties.
108
78
109
-
Here's below an example of using some of this flags:
MicrocksClient got status fortest"64c25f7ddec62569f9a0ed95" - success: true, inProgress: false
122
-
Full TestResult details are available here: http://localhost:8080/#/tests/64c25f7ddec62569f9a0ed95
81
+
### Building from Source
82
+
To build the CLI locally:
83
+
```bash
84
+
make build-local
123
85
```
124
86
125
-
### Import command
126
-
127
-
The `import` command has one argument and common flags with `test` command. You can use it that way:
*`<specificationFile1[:primary],specificationFile2[:primary]>` : Comma separated list of API specs to import with flag telling if it's a primary artifact. Example: `'specs/my-openapi.yaml:true,specs/my-postmancollection.json:false'`
138
-
139
-
The flags:
140
91
141
-
*`--microcksURL` for the Microcks API endpoint,
142
-
*`--keycloakClientId` for the Keycloak Realm Service Account ClientId,
143
-
*`--keycloakClientSecret` for the Keycloak Realm Service Account ClientSecret.
144
-
145
-
> Since `0.5.2` release, `microcks-cli` also works in unauthenticated mode, without Keycloak being deployed and configured with your Microcks instance. However, you still have to specify the Keycloak flags on the command even if you put random values there. For eg. `--keycloakClientId=foo --keycloakClientSecret=bar`.
0 commit comments