Skip to content

move pulumi_aws lambda functions to CapeLambdaFunction #319

@thecaffiend

Description

@thecaffiend

The APIGW lambda authorizer in the API was changed over during implementation of #318 (when the CapeLambdaFunction came into being). There are 4 other usages that should be swapped over for consistency (not line numbers could change based on other changes in other issues):

capeinfra/meta/capemeta.py:883:        report_data_lambda = aws.lambda_.Function(
capeinfra/resources/api.py:207:            handler_lambda = aws.lambda_.Function(
capeinfra/datalake/datalake.py:473:        self.qmsg_handler = aws.lambda_.Function(
capeinfra/datalake/datalake.py:554:        new_object_handler = aws.lambda_.Function(

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0Highest Priority

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions