Skip to content

Updating publish instruction for eusc aws account #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sumoanema merged 2 commits into from
Jun 3, 2026
Merged

Updating publish instruction for eusc aws account #33

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cedfa20
Updating publish instruction for eusc aws account
sumoanema Jun 3, 2026
f962946
Apply suggestions from code review
sumoanema Jun 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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=<sumo content profile>`
1. Update the layer version in *config/version.go*.
Expand All @@ -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
Comment thread
sumoanema marked this conversation as resolved.
Outdated
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.
Comment thread
sumoanema marked this conversation as resolved.
Outdated
`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.
Comment thread
sumoanema marked this conversation as resolved.
Outdated
`export AWS_PROFILE_EUSC=<eusc production profile>`
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.
Comment thread
sumoanema marked this conversation as resolved.
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.
Comment thread
sumoanema marked this conversation as resolved.

### 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).
Expand Down
Loading