Skip to content
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.

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

Fix: [AEA-0000] - fix deployment following adding status endpoint #184

Merged
merged 3 commits into from
Apr 30, 2024
Merged
Changes from all commits
Commits
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
5 changes: 3 additions & 2 deletions SAMtemplates/apis/main.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -226,21 +226,22 @@ Resources:
IntegrationHttpMethod: POST
Uri: !Sub arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${StatusLambdaFunctionArn}/invocations

# if you add a new endpoint, then change the stage name
# if you add a new endpoint, then need to manually force a deployment
# aws apigateway create-deployment --rest-api-id <CHANGE ME> --stage-name prod --description 'Deployed from CLI'
RestApiGatewayDeployment:
Type: AWS::ApiGateway::Deployment
DependsOn:
- UpdatePrescriptionStatusMethod
- StatusLambdaMethod
Properties:
RestApiId: !Ref RestApiGateway
StageName: prod-v1

RestApiGatewayStage:
Type: AWS::ApiGateway::Stage
Properties:
RestApiId: !Ref RestApiGateway
DeploymentId: !Ref RestApiGatewayDeployment
StageName: prod
TracingEnabled: true
AccessLogSetting:
DestinationArn: !GetAtt RestApiGatewayResources.Outputs.ApiGwAccessLogsArn
Expand Down