CICD Apply fix

[DCCoder90]

No description provided.

In general, the fix is to avoid dynamically indexing into secrets and instead reference only the specific secrets that are required, using static names. For matrix workflows, that usually means either (1) mapping each matrix entry to a concrete secret name and using conditionals or distinct jobs, or (2) if the value is not truly secret, storing it in a non‑secret context like vars or the matrix definition itself.

For this workflow, TF_WORKSPACE appears to be a Terraform Cloud workspace identifier, not a secret. The cleanest fix that does not change behavior is:

• Move the workspace values from secrets into non‑secret configuration (the matrix itself).
• Set TF_WORKSPACE directly from the matrix value instead of from secrets[...].

Concretely, within .github/workflows/run-apply.yml:

1. Change the matrix.include entries so that workspace contains the actual Terraform Cloud workspace name (e.g., core and apps, or whatever the current secret values are) instead of the names of secrets.
2. Update the env block to set TF_WORKSPACE: ${{ matrix.workspace }} instead of TF_WORKSPACE: ${{ secrets[matrix.workspace] }}.

This removes the dynamic secret access and ensures the runner only receives the explicitly referenced secrets (TF_API_TOKEN and TF_ORGANIZATION), preserving existing functionality of choosing a workspace per matrix entry.