Skip to content

Latest commit

 

History

History
411 lines (289 loc) · 10.6 KB

README.md

File metadata and controls

411 lines (289 loc) · 10.6 KB
Raw

Civil customised version of CCD Docker 🐳

Prerequisites

  • Docker
    • Memory and CPU allocations may need to be increased for successful execution of ccd applications altogether. We recommend using the following settings for Docker:
      • CPUs: 4
      • Memory: 11.25GB
      • Swap: 2.5GB
  • Azure CLI - minimum version 2.0.57
  • jq Json Processor

Local environment setup

  1. Login to the Azure Container registry:
./ccd login

Note: If you experience any error with the above command, try az login or az login --use-device-code first

  1. Pulling latest Docker images:
./ccd compose pull

If you're seeing errors when pulling images, run the following command:

az acr login --name hmctspublic --subscription 8999dec3-0104-4a27-94ee-6588559729d1

and try pulling images again.

  1. Add the docmosis API key to compose/docmosis.yml, or export the DOCMOSIS_KEY variable in your ~/.zshrc file.

To generate a new API key click here.

  1. Enable docker compose defaults

Note: If you'd like to run OCMC services as well, append ocmc line in defaults.conf. DO NOT COMMIT THIS CHANGE!

./ccd enable defaults
  1. Create docker network
docker network create ccd-network
  1. Creating and starting the containers:
./ccd compose up -d

Note: Not all the containers may come up on first try. Run the command again a couple minutes later to bring up the remaining. This is because some containers require others, and although the container itself is up, the application isn't yet. Note: If dm-store won't stay up, logging the error blobStorageReadService, stop and delete the containers compose_azure-storage-emulator-azurite_1 and dm-store, then run

docker volume rm compose_ccd-docker-azure-blob-data
./ccd compose up -d
  1. Scripts to create test users and import CCD definitions are located in bin directory.

To add services:

IDAM_ADMIN_USER=<enter email> IDAM_ADMIN_PASSWORD=<enter password> ./bin/add-services.sh

To add roles required to import ccd definition:

IDAM_ADMIN_USER=<enter email> IDAM_ADMIN_PASSWORD=<enter password> ./bin/add-roles.sh

To add users:

./bin/add-users.sh

IDAM_ADMIN_USER and IDAM_ADMIN_PASSWORD details can be found on Confluence.

To add role assignments:

./bin/add-role-assignments.sh
  1. Process and import ccd definition from civil-ccd-definition repo

Note: These next scripts requires you to have the other civil repositories cloned to the same directory so if you don't have those, go get them.

./bin/process-and-import-ccd-definition.sh "-e *-prod.json,AuthorisationCaseType-shuttered.json"

The -e option allows you to ignore some files in ccd-definition when building the UI. If you get messages about duplicated fields, or case_event, case_field keys, most probably there are several json files declaring different versions of the same field. Note: If you have chosen to run OCMC services as well in step 4, you need to import CMC CCD definition. You can do so by running:

docker-compose -f compose/cmc-ccd-definition-importer.yml up cmc-ccd-definition-importer

For OCMC, add the following lines to the hosts /etc/hosts file:

127.0.0.1 idam-web-public

127.0.0.1 claim-store-api

  1. Upload Camunda diagrams from civil-camunda-bpmn-definition repo
./bin/import-bpmn-diagram.sh

Stopping

To stop the containers and preserve the data run:

/ccd compose down -t 1

Removing

To remove the containers and their data, run:

./ccd compose down -v
docker system prune -a --volumes

Notes

To enable stubbing of the PROXY_PAYMENTS set the PROXY_PAYMENTS_STUB environment variable to the desired url.

mocks/wiremock/__files/crd/categories.json was created based on ListOfValues_24.01.2023.csv which contains errors. When updated version of CSV is issued, the JSON has to be updated as well.

Elastic search

Information

compose/elasticsearch.yml has been updated with latest image. For this to work the jursdiction will need to be added to the logstash repo: ccd-logastash.

To enable ElasticSearch compose run following:

./ccd backend dm-store sidam sidam-local sidam-local-ccd xui elasticsearch

Please see packer_images directory in the logstash repo and specific adoption files for further info.

When adding a CCD definition file elastic search indexes will be created. To verify, you can hit the elastic search api directly on localhost:9200 with the following command. It will return all stored indexes.

curl -X GET http://localhost:9200/jurisdiction_cases

The following command will return all cases currently indexed.

curl -X GET http://localhost:9200/jurisdiction_cases/_search

Note: If you start elastic search after having existing cases, these cases will not be searchable using ES.

CoreCaseDataApi Elastic Search Endpoint

You can search on local envs using this endpoint: localhost:4452/searchCases?ctid=case_type

An example of a JSON search query which would return any cases where the reference is 1234:

{
  "query": {
    "match": {
      "reference": "1234"
    }
  }
}

Please see ES docs - start searching for more examples of search queries.

Example curl:

curl --location --request POST 'localhost:4452/searchCases?ctid=case_type' \
--header 'Content-Type: application/json' \
--header 'Authorization: <auth-token> \
--header 'ServiceAuthorization: <service-auth-token> \
--data-raw '{
  "query": {
    "match" : {
      "reference" : "1234"
    }
  }
}'

Example response:

{
  "total": 1,
  "cases": [
    {
      "id": 1234,
      "jurisdiction": "jurisdiction",
      "state": "Open",
      "version": null,
      "case_type_id": "case_type",
      "created_date": "2020-03-09T16:05:01.742",
      "last_modified": "2020-03-09T16:05:01.745",
      "security_classification": "PUBLIC",
      "case_data": {},
      "data_classification": {
        "creatorId": "PUBLIC"
      },
      "after_submit_callback_response": null,
      "callback_response_status_code": null,
      "callback_response_status": null,
      "delete_draft_response_status_code": null,
      "delete_draft_response_status": null,
      "security_classifications": {
        "creatorId": "PUBLIC"
      }
    }
  ]
}

Elastic search limit of total fields has been exceeded

If you see this message, there are too many field indexes in Elastic Search. By default, all fields declared in ccd-definition are indexed. To prevent one from doing so, use Searchable: N in its declaration. However, if you want the indexes for al of them, you can change the Elastic Search limit as follows:

curl -XPUT localhost:9200/*_cases*/_settings -H 'Content-Type: application/json' -d '{ "index.mapping.total_fields.limit" : 12000 }'

Camunda

Camunda is part of defaults.conf file, so it is enabled by default.

To enable the compose file manually run the following:

./ccd enable backend dm-store sidam sidam-local sidam-local-ccd xui camunda elasticsearch

Camunda is available at http://localhost:9404/. To login into the cockpit application use:

username: demo

password: demo

Within Cockpit, you can find information around deployed processes.

The easiest way to deploy a process is via the Camunda Modeler and setting the REST endpoint value to http://localhost:9404/engine-rest. However, this can also be done via the REST API. You can find full documentation of the REST API here.

Deployments

To delete all deployments and process instances from your local env run the script:

./bin/reset-camunda.sh

To deploy new bpmn diagrams stored in civil-camunda-bpmn-definition repo run the script:

./bin/import-bpmn-diagram.sh .

Idam Stub

Prerequisites:

Add following line to your /etc/hosts:

127.0.0.1	ccd-test-stubs-service

Enable stub

To use the Idam stub instead of real service follow the steps:

  • Make sure you are in root directory (civil-sdk)
  • Run the command to enable the stub and rebuild local environment:
export IDAM_STUB_ENABLED=true && ./bin/toggle-idam-stub.sh
  • Run civil-service with profiles:
spring.profiles.active=local,idam-stub

If you want to run functional tests in new terminal tab, the env variable needs to be re-exported or added to ~/.zshrc file:

export IDAM_STUB_ENABLED=true

Switching back to real Idam

  • Run the command to disable stub and rebuild local environment:
unset IDAM_STUB_ENABLED && ./bin/toggle-idam-stub.sh
  • Run civil-service with the following profiles:
spring.profiles.active=local

Useful scripts

Reset local wiremock mappings

curl -X DELETE http://localhost:8765/__admin/mappings && curl -X POST http://localhost:8765/__admin/mappings/reset

Connect to preview database

kubectl port-forward {YOUR_PR_POSTGRES_POD} -n civil 9999:5432

Example:

kubectl port-forward civil-service-pr-168-postgresql-0 -n civil 9999:5432

After running the command you can connect to postgres database on localhost:9999 with hmcts user and password.

Remove stuck PR

./bin/remove-stuck-pr {REPOSITORY} {PR_NUMBER}

This script supports either ccd, service, or camunda for REPOSITORY.

Example:

./bin/remove-stuck-pr service 165
./bin/remove-stuck-pr.sh general-applications 306
./bin/remove-stuck-pr.sh general-apps-ccd-definition 306

###Find chart versions for applications

./bin/find-chart-version.sh {APPLICATION_CHART_NAME}

Example:

./bin/find-chart-version.sh camunda-bpm

Run tests against AAT

./run-tests-aat.sh {S2S_SECRET} {TEST_TYPE} {SHOW_BROWSER_WINDOW}

S2S secret needs to be provided, it's microservicekey-civil-service from civil-aat vault. Example:

./run-tests-aat.sh SECRET_FROM_AAT_VAULT e2e true

LICENSE

This project is licensed under the MIT License - see the LICENSE file for details.