Skip to content

Conversation

@IanButterworth
Copy link
Member

Runs serverless package on PRs/pushes that modify web service files to catch config errors before merge.

IanButterworth and others added 8 commits January 7, 2026 12:27
Runs serverless package on PRs/pushes that modify web service files
to catch config errors before merge.

Co-authored-by: Claude <[email protected]>
Serverless v3+ has native support for AWS pseudo parameters.
Use ${aws:region} and ${aws:accountId} instead of #{AWS::...} syntax.

Co-authored-by: Claude <[email protected]>
Serverless v4 requires authentication. Pass access key from secrets.

Co-authored-by: Claude <[email protected]>
(cherry picked from commit 3fbf9a6)
The ${aws:region} and ${aws:accountId} variables need AWS credentials
to resolve, even for packaging. Use dummy values since we're not deploying.

Co-authored-by: Claude <[email protected]>
Replace ${aws:region} and ${aws:accountId} with CloudFormation
intrinsic functions (${AWS::Region}, ${AWS::AccountId}) which are
resolved at deploy time, not package time.

Co-authored-by: Claude <[email protected]>
Serverless v4 requires real AWS credentials for packaging.
Use aws-actions/configure-aws-credentials with OIDC for secure,
short-lived credentials without storing long-term secrets.

Requires one-time AWS setup:
1. Create IAM Identity Provider for GitHub OIDC
2. Create IAM Role with trust policy for this repo
3. Add AWS_ROLE_ARN to repository secrets

Co-authored-by: Claude <[email protected]>
Pin to Serverless v3.39 which does not require AWS credentials for
packaging validation. Added docs/TODO-serverless-v4.md with instructions
for upgrading to v4 when AWS OIDC is configured.

Co-authored-by: Claude <[email protected]>
@IanButterworth IanButterworth marked this pull request as ready for review January 8, 2026 14:41
@IanButterworth IanButterworth merged commit c5e620f into master Jan 8, 2026
3 checks passed
@IanButterworth IanButterworth deleted the ib/server_test branch January 8, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants