Automated the layer version increment process

Author: sdangol

.github/workflows/update_ssm.yml

@@ -5,7 +5,6 @@
 # * environment: will prefix /beta/ into the parameter
 # * write_latest: will create a latest alias instead of a version number in the parameter
 # * package_version: semantic version number of the released layer (3.x.y)
-# * layer_version: this is sequential layer version from the ARN
 #
 # A successful parameter would look similar to:
 #   /aws/service/powertools/python/arm64/python3.8/3.1.0
@@ -41,11 +40,6 @@ on:
         type: string
         required: true
 
-      layer_version:
-        description: Layer version
-        type: string
-        required: true
-
 name: SSM Parameters
 run-name: SSM Parameters - TypeScript
 
@@ -107,15 +101,22 @@ jobs:
           # Dynamic secret access is safe here - secrets are scoped per environment
           role-to-assume: ${{ secrets[format('{0}', steps.transform.outputs.CONVERTED_REGION)] }}
           mask-aws-account-id: true
+      - id: get-version
+        env:
+          prefix: ${{ inputs.environment == 'beta' && '/aws/service/powertools/beta' || '/aws/service/powertools' }}
+        run: |
+          current_layer_version=$(aws ssm get-parameter --name ${{ env.prefix }}/typescript/generic/all/${{ inputs.package_version }} --query Parameter.Value --output text --region us-east-1)
+          new_layer_version=$((current_layer_version + 1))
+          echo "new_layer_version=$new_layer_version" >> "$GITHUB_OUTPUT"
       - id: write-version
         env:
           prefix: ${{ inputs.environment == 'beta' && '/aws/service/powertools/beta' || '/aws/service/powertools' }}
         run: |
-          aws ssm put-parameter --name ${{ env.prefix }}/typescript/generic/all/${{ inputs.package_version }} --value "arn:aws:lambda:${{ matrix.region }}:094274105915:layer:AWSLambdaPowertoolsTypeScriptV2:${{ inputs.layer_version }}" --type String --overwrite
+          aws ssm put-parameter --name ${{ env.prefix }}/typescript/generic/all/${{ inputs.package_version }} --value "arn:aws:lambda:${{ matrix.region }}:094274105915:layer:AWSLambdaPowertoolsTypeScriptV2:${{ steps.get-version.outputs.new_layer_version }}" --type String --overwrite
 
       - id: write-latest
         if: inputs.write_latest == true
         env:
           prefix: ${{ inputs.environment == 'beta' && '/aws/service/powertools/beta' || '/aws/service/powertools' }}
         run: |
-          aws ssm put-parameter --name ${{ env.prefix }}/typescript/generic/all/latest --value "arn:aws:lambda:${{ matrix.region }}:094274105915:layer:AWSLambdaPowertoolsTypeScriptV2:${{ inputs.layer_version }}" --type String --overwrite
+          aws ssm put-parameter --name ${{ env.prefix }}/typescript/generic/all/latest --value "arn:aws:lambda:${{ matrix.region }}:094274105915:layer:AWSLambdaPowertoolsTypeScriptV2:${{ steps.get-version.outputs.new_layer_version }}" --type String --overwrite

docs/maintainers.md

@@ -191,20 +191,12 @@ This will publish the Lambda layer to the AWS China (Beijing) Region.
 9. **Merge docs PR**: Once the `Layer Deployment (Partition)` workflow for the production China partition is complete,
 merge the PR from step 4 to update the documentation with the new version.
 10. **Update SSM Parameters (Beta)**: Run the `SSM Parameters` workflow with the `main` branch, targeting the `beta`
-deployment environment, and using the package version from npm (i.e., `2.20.0`) and Lambda layer version from step 4.
+deployment environment, and using the package version from npm (i.e., `2.20.0`).
 This will update the SSM parameters with the new version.
-11. **Verify SSM Parameters (Beta)**: Use the AWS CLI to verify that the SSM parameters were updated correctly. Run
-the following command: `aws ssm get-parameter --name=/aws/service/powertools/beta/typescript/generic/all/latest`
-and `aws ssm get-parameter --name=/aws/service/powertools/beta/typescript/generic/all/<version>` to verify that the
-SSM parameters were updated correctly.
-12. **Update SSM Parameters (Prod)**: Run the `SSM Parameters` workflow with the `main` branch, targeting the `prod`
-deployment environment, and using the package version from npm (i.e., `2.20.0`) and Lambda layer version from step 4.
+11. **Update SSM Parameters (Prod)**: Run the `SSM Parameters` workflow with the `main` branch, targeting the `prod`
+deployment environment, and using the package version from npm (i.e., `2.20.0`).
 This will update the SSM parameters with the new version.
-13. **Verify SSM Parameters (Prod)**: Use the AWS CLI to verify that the SSM parameters were updated correctly. Run
-the following command: `aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest`
-and `aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/<version>` to verify that the
-SSM parameters were updated correctly.
-14. **Update Docs**: Run the `Rebuild latest docs` workflow with the `main` branch using the package version from
+12. **Update Docs**: Run the `Rebuild latest docs` workflow with the `main` branch using the package version from
 npm (i.e. `2.20.0`). This will update the documentation with the new version.
 
 Once complete, you can start drafting the release notes to let customers know **what changed and what's in it for them (a.k.a why they should care)**. We have guidelines in the release notes section so you know what good looks like.