Skip to content

What to do when a part of the stack changes

Jump to bottom
E. Lynette Rayle edited this page May 13, 2022 · 1 revision

A change in Questioning Authority (QA) happens when a new release of QA becomes available. You can track changes to QA at rubygems.org/gems/qa.

If you want to change the QA version, you will need to do all the steps below.

If you made changes to the Admin UI in LD4P/qa_server, after making changes through the regular PR process, start at 2.3 in the steps below.

  1. check that the new QA version is compatible with the restrictions defined in LD4P/qa_server qa_server.gemspec
    1. If NOT, update the version restrictions in LD4P/qa_server and release a new version of the engine. NOTE: Depending on the changes in QA, you may have to update code in LD4P/qa_server to make it compatible with the new version of QA.
    2. If it is, no changes needed in LD4P/qa_server
  2. check that the new QA version is compatible with the restrictions defined in LD4P/qa_server_container Gemfile
    1. If NOT, update the version restrictions in LD4P/qa_server_container.
    2. Once compatible, use bundle update qa to update the QA version.
    3. Assign a new version for LD4P/qa_server_container in /VERSION following Semantic Versioning NOTE: In this case, the level of the version change will be driven by the significance of the change in QA.
    4. Describe the changes that will be seen when using the new version of LD4P/qa_server_container in /CHANGELOG.md.
    5. Create a PR with the changes to Gemfile, Gemfile.lock, VERSION, and CHANGELOG.md.
    6. If you are confident in the changes, you can merge the PR into dev branch which will trigger a build and deploy the -int image to the AWS-ECR private repo. If you want to test before merging into dev branch, you can use GitHub action Push image of dev branch to integration image at Amazon ECR as ld4p/qa_authority_lookup-int -> Run workflow -> select your branch -> Run workflow.
      1. To test -int image, run GitHub action redeploy-int in cul-it/qa_server_aws_deploy
      2. test on http://lookup-int.ld4l.org
    7. When happy with the image, create a PR to merge into dev branch into main branch and merge it. This will trigger a build and deploy the -stg image to the AWS-ECR private repo.
      1. To test -stg image, run GitHub action redeploy-stg in cul-it/qa_server_aws_deploy
      2. test on http://lookup-stg.ld4l.org
    8. When happy, create a release in GitHub from the main branch. This will trigger a build and deploy of the branches tagged code to the production public image of the lookup server. The images will be tagged :latest and with the version in /VERSION.
  3. Redeploy cul-it/qa_server_aws_deploy using GitHub action redeploy-prod to put it in production at http://lookup.ld4l.org.
Clone this wiki locally