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
Copy file name to clipboardExpand all lines: README.md
+43-15Lines changed: 43 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,19 +120,21 @@ The list of allowable commodity values is:
120
120
5. elasticsearch7
121
121
6. nginx
122
122
7. rabbitmq
123
-
8. redis
124
-
9. swagger
125
-
10. wiremock
126
-
11. squid
127
-
12. auth
128
-
13. cadence
129
-
14. cadence-web
130
-
15. activemq
131
-
16. ibmmq
132
-
17. localstack
133
-
18. valkey
134
-
19. prometheus
135
-
20. grafana
123
+
8. rabbitmq-4
124
+
9. redis
125
+
10. swagger
126
+
11. wiremock
127
+
12. squid
128
+
13. auth
129
+
14. cadence
130
+
15. cadence-web
131
+
16. activemq
132
+
17. ibmmq
133
+
18. localstack
134
+
19. valkey
135
+
20. prometheus
136
+
21. grafana
137
+
22. govuk-one-login
136
138
137
139
The file may optionally also indicate that one or more services are resource intensive ("expensive") when starting up. The dev env will start those containers seperately - 3 at a time - and wait until each are declared healthy (or crash and get restarted 10 times) before starting any more.
138
140
@@ -220,18 +222,34 @@ This is a file that contains stub mappings that Wiremock will pick up and use, a
220
222
221
223
This is a directory that can contain multiple stub mappings files that Wiremock will pick up and use. The files should all be in the same format as the example above. If such a wiremock directory exists, it will take precedence over any `wiremock-fragment.json` file.
222
224
223
-
##### RabbitMQ
225
+
##### RabbitMQ 3
224
226
225
227
There are no fragments needed when using this. The Management Console will be available on <http://localhost:15672> (guest/guest).
226
228
227
-
Rabbit is available over port 5672 and TLS on port 5671.
229
+
RabbitMQ 3 is available over port 5672 and TLS on port 5671.
228
230
229
231
TLS presents a self signed cert. If verification is needed then use the provided [ca certificate](scripts/docker/rabbitmq/certs/ca_certificate.crt). The host has been set to `rabbitmq` for host verification in most common libraries, although will only work within the docker network.
230
232
231
233
MTLS is not enabled, although a [client certificate pem](scripts/docker/rabbitmq/certs/client_certificate.pem) and [client key pem](scripts/docker/rabbitmq/certs/client_key.pem) have been generated as part of the certificate set for potential future use.
232
234
233
235
Currently, only the `rabbitmq_management`, `rabbitmq_consistent_hash_exchange`, `rabbitmq_shovel`, `rabbitmq_shovel_management`, `rabbitmq_stream` and `rabbitmq_prometheus` plugins are enabled.
234
236
237
+
The default queue type for queues in RabbitMQ 3 is `classic`.
238
+
239
+
##### RabbitMQ 4
240
+
241
+
There are no fragments needed when using this. The Management Console will be available on <http://localhost:15682> (guest/guest).
242
+
243
+
RabbitMQ 4 is available over port 5682 and TLS on port 5681.
244
+
245
+
TLS presents a self signed cert. If verification is needed then use the provided [ca certificate](scripts/docker/rabbitmq/certs/ca_certificate.crt). The host has been set to `rabbitmq` for host verification in most common libraries, although will only work within the docker network.
246
+
247
+
MTLS is not enabled, although a [client certificate pem](scripts/docker/rabbitmq/certs/client_certificate.pem) and [client key pem](scripts/docker/rabbitmq/certs/client_key.pem) have been generated as part of the certificate set for potential future use.
248
+
249
+
Currently, only the `rabbitmq_management`, `rabbitmq_consistent_hash_exchange`, `rabbitmq_shovel`, `rabbitmq_shovel_management`, `rabbitmq_stream` and `rabbitmq_prometheus` plugins are enabled.
250
+
251
+
The default queue type for queues in RabbitMQ 4 is `quorum`.
252
+
235
253
##### ActiveMQ
236
254
237
255
There are no fragments needed when using this. The Management Console will be available on <http://localhost:8161> (admin/admin).
@@ -362,6 +380,16 @@ bashin redis
362
380
redis-cli monitor
363
381
```
364
382
383
+
###### GOV.UK One Login
384
+
385
+
The GOV.UK One Login simulator is a development tool that lets you run end-to-end tests, so you can:
386
+
387
+
- test and verify specific user information such as names and email addresses
388
+
- request specific error codes and learn more about what they mean in a test environment
389
+
- test integrations with GOV.UK One Login without going through account creation
390
+
391
+
See [documentation](https://github.com/govuk-one-login/simulator).
0 commit comments