From cedfa2021bc4c8afb4bea1767bac5684c00115d7 Mon Sep 17 00:00:00 2001 From: Alekh Nema Date: Wed, 3 Jun 2026 21:05:50 +0530 Subject: [PATCH 1/2] Updating publish instruction for eusc aws account --- CONTRIBUTING.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d5a069c..0a4227d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -50,6 +50,7 @@ First of all, thanks for contributing!. Before contributing please read the [COD because AWS caches the layer code internally. - However, once you update or redeploy them, `v10` will no longer be available. +#### Releasing layer for Commercial AWS 1. Change the *AWS_PROFILE* environment variable using below command. The profile should point to sumocontent aws account. `export AWS_PROFILE=` 1. Update the layer version in *config/version.go*. @@ -62,6 +63,21 @@ First of all, thanks for contributing!. Before contributing please read the [COD 1. Run the following command to verify that the layer version is published across regions: `sh verify_layer_versions.sh` +#### Releasing layer for EUSC(Euorpean Sovereign cloud) AWS +We have a seperate EUSC production aws account where we need to publish. +1. You need to get the EUSC accessid and accesskey via dev cli. + `dev hcvault login` + `dev hcvault cli_env -a esc-production` +1. Change the *AWS_PROFILE_EUSC* environment variable using below command. The profile should point to eusc production aws account. + `export AWS_PROFILE_EUSC=` +1. Update the layer version in *config/version.go*. +1. Go to scripts folder + `cd scripts/` +1. Change the layer_name variable in zip.sh to avoid replacing the prod. +1. Run the following command to publish the layer: + `sh zip_special_partitions.sh` +1. The zip file generated by previous step should have `extensions` folder in it, which should consist of the binary for the extension. + ### Github Release - The new extension binary and zip files gets released automatically after the tags are pushed using Github actions(Refer tagged-release in https://github.com/marvinpinto/action-automatic-releases). From f9629466a3c6c868546dd9320143ebbbf196795a Mon Sep 17 00:00:00 2001 From: Alekh Nema <91047769+sumoanema@users.noreply.github.com> Date: Wed, 3 Jun 2026 21:11:13 +0530 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0a4227d..f5c50d4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -63,12 +63,12 @@ First of all, thanks for contributing!. Before contributing please read the [COD 1. Run the following command to verify that the layer version is published across regions: `sh verify_layer_versions.sh` -#### Releasing layer for EUSC(Euorpean Sovereign cloud) AWS -We have a seperate EUSC production aws account where we need to publish. -1. You need to get the EUSC accessid and accesskey via dev cli. +#### Releasing layer for EUSC (European Sovereign Cloud) AWS +We have a separate EUSC production AWS account where we need to publish the layer. +1. Get the EUSC AWS access key ID and secret access key via the dev CLI: `dev hcvault login` `dev hcvault cli_env -a esc-production` -1. Change the *AWS_PROFILE_EUSC* environment variable using below command. The profile should point to eusc production aws account. +1. Set the *AWS_PROFILE_EUSC* environment variable using the command below. The profile should point to the EUSC production AWS account. `export AWS_PROFILE_EUSC=` 1. Update the layer version in *config/version.go*. 1. Go to scripts folder