awslabs / awslabs/aws-lambda-powershell-runtime
What is the status of this vs. AWSLambdaPSCore?
- Vorherrschende Sprache
- PowerShell
- Sterne
- 65
- Forks
- 21
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
I am confused by the existence of this project.
Is it a replacement for AWSLambdaPSCore? If so, why isn't this project formally documented in the AWS documentation as an alternative to that? The doc, AFAIK, still refers only to AWSLambdaPSCore.
A blog post from 2022 and a seven-minute demo YouTube video are insufficient to determine the production viability of this project for pwsh devs want the durability and production support of AWSLambdaPSCore. Is AWS recommending new functions developed in PowerShell should be deployed using this technique? Is there a deprecation date for AWSLambdaPSCore?
These questions, and many more that devs need to assess the production quality and future of this project are unanswered.
Also, I'm not sure that the benefits of editing code in the AWS console outweigh the clumsy (and poorly documented) deployment process and added size. I'd appreciate knowing why running in a container with a layer of indeterminate durability is better than bundling a supported .Net runtime with known, specific versions of AWS.Tools modules.
Clearly, I don't "get it." :-)
Beitragsleitfaden
Rechercherichtung
Start by comparing this project with AWSLambdaPSCore and reviewing the AWS documentation, the 2022 blog post, and the demo video mentioned in the issue. Document whether this runtime is a replacement or recommendation, any AWSLambdaPSCore deprecation timeline, and the production rationale and deployment trade-offs.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- aws, powershell
- Bereich
- cloud, documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100