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

Expose Option: ignorePackageArtifact #1208

Conversation

Leglaw
Copy link

@Leglaw Leglaw commented Apr 6, 2021

This option is helpful for projects not yet ready or able to run the
project using the artifact. Defaults to false. If
ignorePackageArtifact: true is added to the serverless.yml
custom.serverless-offline configuration section, the source files will
be used to run the offline lambda.

This option is helpful for projects not yet ready or able to run the
project using the artifact. Defaults to false. If
`ignorePackageArtifact: true` is added to the serverless.yml
custom.serverless-offline configuration section, the source files will
be used to run the offline lambda.
@pgrzesik
Copy link
Collaborator

pgrzesik commented Jun 1, 2021

Hello @Leglaw - it looks good overall, however, it misses the suggestion from @nponeccop about type for the option. Would you be able to correct it so we can get this merged?

@raytorres280
Copy link

I too am waiting on this feature. I created a relatively useless PR on OP's fork with the one line change. Could really use this.

@AshHeskes
Copy link

Surely this should be the default behaviour anyway? The package option is used for build/deploy. Surely in "offline" mode everyone expects this to be reading src files?

Co-authored-by: nponeccop <andy.melnikov@gmail.com>
@Leglaw
Copy link
Author

Leglaw commented Sep 23, 2022

I've neglected this PR as we're migrating all our services to AWS SAM.

Is anyone else still wanting this feature? If there's still interest and maintainers are ok with the general approach, I'm happy to do work to get this over the finish line.

@Leglaw Leglaw closed this Oct 28, 2022
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.

None yet

6 participants