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

AWS Layers and Powershell? #393

Closed
JustinGrote opened this issue Feb 6, 2019 · 7 comments
Closed

AWS Layers and Powershell? #393

JustinGrote opened this issue Feb 6, 2019 · 7 comments

Comments

@JustinGrote
Copy link

In relation to #319, and the announcement of AWS Layers, is this a potential option to make this simpler? Could the .NET Core Runtime be packaged as a layer, so that the actual Powershell script is far more lightweight and easier to iterate/test? That would be huge, uploading a 22MB file every revision is a major stop gap to rapid development compared to Azure Functions or Azure Automation.

Is there any potential guidance around this?

@klaytaybai klaytaybai added the feature-request A feature should be added or improved. label Feb 8, 2019
@klaytaybai
Copy link

Hi @JustinGrote, thank you for your interest in this! Consider participating in this discussion about using .NET Core with Layers: aws/aws-extensions-for-dotnet-cli#58

@burkasaurusrex
Copy link

Now that Layers have .Net Core support, any chance we could bring them Powershell? It would be awesome to be able to upload modules to layers and then have a -Function-Layers flag for the Publish-AWSPowerShellLambda cmdlet (similar to dotnet lambda deploy-function --function-layers).

@jgard
Copy link

jgard commented Feb 4, 2020

10 months later, any update here?

@pcgeek86
Copy link

@normj any thoughts?

@sgnewman
Copy link

Bueller? Would love for PS modules to be supported in layers.

@normj
Copy link
Member

normj commented Jan 6, 2021

We haven't implemented anything yet for publishing PS modules as a Lambda Layer yet. There is some potentially interesting work we could do there but just haven't prioritized the work yet.

In theory you could zip up your dependent PS modules and publish that as a layer then in your PowerShell script to manually import the modules from the /opt folder that you zipped up in the layer. I haven't tired this but I don't see why it wouldn't work.

@github-actions
Copy link
Contributor

We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants