This change is for developers that want to be able to render the CivicUK API key on the client. This has caused issues in tests recently for @rcantin-w on this PR, where tests were failing due to a hydration issue arising because the client does not not have the API key available while the server does.
This change follows https://github.com/wellcomecollection/wellcomecollection.org/pull/10705 in adding the NEXT_PUBLIC_CIVICUK_API_KEY to the build environment from AWS Secrets Manager using a Buildkite plugin. This is required as in order to inline the API key value for availability client side it needs to be available at build time.
Who is this for?
This change is for developers that want to be able to render the CivicUK API key on the client. This has caused issues in tests recently for @rcantin-w on this PR, where tests were failing due to a hydration issue arising because the client does not not have the API key available while the server does.
Depends on: https://github.com/wellcomecollection/aws-account-infrastructure/pull/21
See: https://wellcome.slack.com/archives/C3TQSF63C/p1717165895658859 for more context on an issue this was causing.
What is it doing for them?
This change follows https://github.com/wellcomecollection/wellcomecollection.org/pull/10705 in adding the
NEXT_PUBLIC_CIVICUK_API_KEY
to the build environment from AWS Secrets Manager using a Buildkite plugin. This is required as in order to inline the API key value for availability client side it needs to be available at build time.See: https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables#bundling-environment-variables-for-the-browser
This change makes use of the forked plugin https://github.com/wellcomecollection/aws-sm-buildkite-plugin (forked to our org to ensure no unknown changes in a module that has secrets access).
How to test
This build should pass: https://buildkite.com/wellcomecollection/wc-dot-org-end-to-end-tests/builds/4424#018fddcc-2661-4c16-b8d5-1e139c60734c