Each of these services can be retrieved from the Wych Public container registry. To access this registry you require credentials. These credentials are available in the service portal or from your account manager.
The Wych Container Registry (WCR) stores and manages private container images and other artifacts, similar to the way Docker Hub stores public Docker container images. You can use the Docker command-line interface (Docker CLI) to login and pull images from WCR.
Docker CLI - You must also have Docker installed locally. Docker provides packages that easily configure Docker on any Linux, macOS, or Windows system.
For best practice to manage login credentials, see the docker login command reference:
docker login wychaustralia.azurecr.io
A successful login will show Login Succeeded once completed.
It is advisable to proxy the request against the WCR, this ensures you don’t have to share the registry credentials with multiple people and you can also scan the images for vulnerabilities before they enter your environment. This approach should be the same for other public repositories such as docker hub or quay.io.
Lets start by pulling the AU Register Auth. This service provides the security, infosec, token and key capabilities of the Register. This version has been designed to support Data Holder testing and can be shared by multiple Data Holder and Tester instances but has a 1:1 relationship with the AU register.
Next we will pull the AU register service. This service represents the ACCC’s AU register service, this version has been designed to support Data Holder testing and so while on an API level it is similar to the ACCC’s service it is fundamentally different in a number of key ways.
Last service to pull requires the others to be ready, this is the Tester. This service is responsible for running the test scenarios and reporting the results of the audit.
This Wych Data Holder Tester (Tester) is the Wych probe for validating the state of a Data Holder solution, this has been designed to support Data Holder testing for ACCC CDR standards with each test verifying a rule as set out in the specifications.
In its simplest form you can send request direction with the auth token for the relevant endpoint and their urls.
This Wych register for AU Data Holder Testing (Register) represents the ACCC’s AU register service, this version has been designed to support Data Holder testing and so while on an API level it is similar to the ACCC’s service it is fundamentally different in a number of key ways.
The register can be shared by multiple Data Holder instance and multiple Data Holder Tester instances. The main consideration here is that the Data Holders must be able to talk to the Register Auth service and vice-versa and the Register Auth must be co-located with the Tester instances as they share a configuration data store.
This Wych register for AU Data Holder Testing (Register) represents the ACCC’s AU register service, this version has been designed to support Data Holder testing and so while on an API level it is similar to the ACCC’s service it is fundamentally different in a number of key ways.
The register can be shared by multiple Data Holder instance and multiple Data Holder Tester instances. The main consideration here is that the Data Holders must be able to talk to the Register and vice-versa and the Register must be co-located with the Tester instances as they share a configuration data store.