SPIKE 🧐 Figure out how env secrets are added to Control Panel via Flux

[michaeljcollinsuk]

User Story

As developers and engineers we are currently uncertain about how environmental secrets are added to the deployment

Value / Purpose

While we still use flux to deploy control panel, we need to be able to add env secrets as required. At the moment we are avoiding adding secrets this way and it is not sustainable.

Useful Contacts

@michaeljcollinsuk

User Types

Developers and platform engineers

Hypothesis

Once we understand and document this process, we will be able to add secrets again.

Proposal

Spend time investigating the existing process for adding env secrets to Control Panel via Flux. Recent attempts to add a secret were unsuccessful, see https://github.com/moj-analytical-services/analytical-platform-flux/pull/1224 for more context and changes that were attempted.

Timebox this to 2 dev-days and if we're unable, raise 2 stories:

1. Move deployment of Control Panel out of Flux
2. Retire Flux as a deployment tool

Additional Information

Slack discussions about the changes attempted

1. https://mojdt.slack.com/archives/C04M8224WCV/p1706724198310519
2. https://mojdt.slack.com/archives/C04M8224WCV/p1706793021693519

See old PR by Yikang which appears to have cleaned up env secrets https://github.com/moj-analytical-services/analytical-platform-flux/pull/1067

Definition of Done

• Secrets can be added/updated or
• Follow-on stories raised.

[github-actions]

This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open.

[github-actions]

This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open.

[github-actions]

This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you!