FSPT-342 - Use basic auth when publishing from Designer to Runner

The Designer makes a backend call to the Runner - specifically to its /publish endpoint, to publish forms. This is the data persistence mechanism in Designer, and is absolutely key to its functionality. We need to make sure that we are passing basic auth credentials as part of this backend request.

We implement this in line with existing precedents in Pre-Award and Post-Award - we hard-code the basic auth credentials in a URL we store in AWS Parameter Store (e.g., http://username:[email protected]) and then import that variable as a secret that can be leveraged with no change required to application code. This is especially important here because the backend request made by Designer is implemented within the git submodule / base repo digital-form-builder, increasing the complexity of any application code changes.

Author: wjrm500

copilot/fsd-form-designer-adapter/manifest.yml

@@ -54,14 +54,14 @@ variables:
   NODE_ENV: production
   CHOKIDAR_USEPOLLING: true
   PREVIEW_URL: "https://application-questions.access-funding.${COPILOT_ENVIRONMENT_NAME}.communities.gov.uk"
-  PUBLISH_URL: "http://fsd-form-runner-adapter:3009"
   AUTH_SERVICE_URL: "https://account.access-funding.${COPILOT_ENVIRONMENT_NAME}.communities.gov.uk"
   SSO_LOGIN_URL: "/sso/login?return_app=form-designer"
   SSO_LOGOUT_URL: "/sessions/sign-out"
   AUTH_COOKIE_NAME: "fsd_user_token"
   AUTH_ENABLED: true
 
 secrets:
+  PUBLISH_URL: /copilot/${COPILOT_APPLICATION_NAME}/${COPILOT_ENVIRONMENT_NAME}/secrets/FORM_RUNNER_INTERNAL_HOST
   RSA256_PUBLIC_KEY_BASE64: /copilot/${COPILOT_APPLICATION_NAME}/${COPILOT_ENVIRONMENT_NAME}/secrets/RSA256_PUBLIC_KEY_BASE64
   SESSION_COOKIE_PASSWORD: /copilot/${COPILOT_APPLICATION_NAME}/${COPILOT_ENVIRONMENT_NAME}/secrets/SESSION_COOKIE_PASSWORD