Skip to content

Deploying individual functions bypasses SSM Fetch plugin #11

@jo3n

Description

@jo3n

This seems to work fine when deploying the whole endpoint, but if using the -f function.js flag it completely bypasses the plugin.

The following works:
sls deploy --stage dev --env development --profile default

The following doesn't:
sls deploy --stage dev --env development --profile default -f myfunction.js

What's more, the second case removes all the fields that were originally injected by the plugin and aren't restored if deployed again using the first command. The only way to "refresh" them is to add another SSM field and run the first command again.

Is this expected behavior?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions