Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

What is the status of this vs. AWSLambdaPSCore?

未关闭
#30 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
aws, powershell

调研方向

首先将此项目与 AWSLambdaPSCore 进行比较,并查阅 AWS 文档、2022 年的博客文章以及 issue 中提到的演示视频。记录此 runtime 是替代方案还是推荐方案、AWSLambdaPSCore 的任何弃用时间表,以及用于生产环境的理由和部署方面的权衡。

由索引模型根据 Issue 内容生成。

描述

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." :-)

主要语言
PowerShell
星标
65
派生
21
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

awslabs/aws-lambda-powershell-runtime 的其他 Issue

查看 awslabs/aws-lambda-powershell-runtime 的全部 Issue

相似的 Issue

更多 Cloud Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。