read secrets in the function

Author: v1v

.buildkite/scripts/steps/ess.ps1

@@ -25,6 +25,32 @@ function ess_up {
 
   # Store the cluster name as a meta-data
   & buildkite-agent meta-data set cluster-name $ClusterName
+
+  # Load the ESS stack secrets
+  # QUESTION: should we support the case when using the ESS stack in local environment?
+  & oblt-cli cluster secrets env --cluster-name $ClusterName --output-file="secrets.env"
+
+  # Load environment variables from secrets.env
+  $envFile = Join-Path $PSScriptRoot "secrets.env"
+
+  if (Test-Path $envFile) {
+      Get-Content $envFile | ForEach-Object {
+          $name, $value = $_.split('=', 2)
+          if ($name -and $value) {
+              # Remove any surrounding quotes from the value
+              $value = $value.Trim('"''')
+
+              # Set the environment variable
+              [System.Environment]::SetEnvironmentVariable($name.Trim(), $value)
+              Write-Output "Set environment variable: $($name.Trim())"
+          }
+      }
+      Write-Output "Environment variables loaded successfully from $envFile" -ForegroundColor Green
+      Remove-Item -Path $envFile -Force -ErrorAction Stop
+  } else {
+      Write-Error "secrets.env file not found at $envFile"
+      return 1
+  }
 }
 
 function ess_down {  

.buildkite/scripts/steps/ess.sh

@@ -24,6 +24,14 @@ function ess_up() {
 
   # Store the cluster name as a meta-data
   buildkite-agent meta-data set cluster-name "${CLUSTER_NAME}"
+
+  # Load the ESS stack secrets
+  # QUESTION: should we support the case when using the ESS stack in local environment?
+  oblt-cli cluster secrets env --cluster-name="${CLUSTER_NAME}" --output-file="secrets.env"
+
+  # Source the secrets file
+  source "secrets.env" || rm "secrets.env"
+  rm secrets.env || true
 }
 
 function ess_down() {

.buildkite/scripts/steps/integration_tests_tf.ps1

@@ -29,15 +29,6 @@ try {
     # Get-Ess-Stack will start the ESS stack if it is a BK retry, otherwise it will retrieve ESS stack metadata
     Get-Ess-Stack -StackVersion $PACKAGE_VERSION
 
-    # Load the ESS stack secrets
-    # Get the cluster name from the meta-data (CI specific)
-    # QUESTION: should we support the case when using the ESS stack in local environment?
-    $ClusterName = & buildkite-agent meta-data get cluster-name
-    & oblt-cli cluster secrets env --cluster-nam $ClusterName --output-file="env.sh"
-
-    # TODO: source the secrets file
-    source "${PWD}/env.sh" || rm "${PWD}/env.sh"
-
     & "$PWD\.buildkite\scripts\buildkite-integration-tests.ps1" $GROUP_NAME $TEST_SUDO
     $TestsExitCode = $LASTEXITCODE
     if ($TestsExitCode -ne 0)

.buildkite/scripts/steps/integration_tests_tf.sh

@@ -39,16 +39,6 @@ if [[ "${BUILDKITE_RETRY_COUNT}" -gt 0 ]]; then
   preinstall_fleet_packages
 fi
 
-# Load the ESS stack secrets
-# Get the cluster name from the meta-data (CI specific)
-# QUESTION: should we support the case when using the ESS stack in local environment?
-CLUSTER_NAME="$(buildkite-agent meta-data get cluster-name)"
-
-oblt-cli cluster secrets env --cluster-name="${CLUSTER_NAME}" --output-file="${PWD}/env.sh"
-
-# Source the secrets file
-source "${PWD}/env.sh" || rm "${PWD}/env.sh"
-
 # Run integration tests
 echo "~~~ Running integration tests"