This document assumes you have followed the instructions in the main README for How to create a new register in an existing environment so that at this point going to https://register-name.register.gov.uk/ shows Register undefined.
Get the credentials from registers-pass:
registers-pass show beta/app/mint/$register-name
Ensure you have the RAILS_MASTER_KEY environment variable set:
export RAILS_MASTER_KEY=`registers-pass show registers/app/manager/store`
From your managing-registers checkout directory run:
rails secrets:edit
Add credentials for new register and save file
Commit changes to config/secrets.yml.enc to a branch
Raise a PR and merge to master
Note: this step may be done by a Data Analyst or a Developer. All other steps can only be done by a Developer.
Create a pull-request (example) in registry-data moving all register data associated with the register to be promoted into the /beta directory. This should include any new fields added to the /field subdirectory, a new file in the /register subdirectory as well as a new subdirectory for the new register itself. Merge this into master.
Follow the instructions in Loading a new field or register and run the script for each new field associated with the register, the register itself and any new datatypes.
Registers load a config file from S3 at start-up, this must be updated to reflect the newly created registers and fields as a prerequisite to loading data.
Run: ansible-playbook refresh_register_field_config_in_s3.yml -e vpc=beta
openregister-java (ORJ) must be re-deployed to pick up the S3 config changes we made in the previous step.
From the CodePipeline console click Release Change to re-deploy the current master build and complete each step of the pipeline.
Make sure you have checked out the .tsv file containing the user entries to be loaded. Follow the steps in Loading or updating the data for a register making sure to enter no when prompted if you want to delete the existing register.