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

Api Versioning

未关闭
#153 2 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

@naorpeled 已经在做这个了。

开始于 2024年5月4日。

评估

这个 Issue 还没有评估数据。

描述

Hey Jeremy,

This is more a question than a problem. I'm trying to implement api versioning based on path but then I need to change the lambda-api configuration to use the base property with v1, v2, etc...

Right now we are configuring the custom domain names in the api gateway like the following:
example-dev.example.com/v1
example-dev.example.com/v2

Each domain points to a different lambda function on a different cloudformation stack, we are not using the available stages on Api Gateway we always use Prod and have one cloudformation stack per environment.

I noticed on the lambda-api code that you parse the request using event's path property which includes the v1 from the custom domain mapping. Is there any option to use the resource property instead(resource property doesn't include mapping, so no v1 on it), in this case I don't need to use base property on the framework config and I can have it working on all my stacks, no matter which version.

I'm open to suggestions, maybe we are not doing the best way. What do you recommend.

主要语言
JavaScript
星标
1.5k
派生
127
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

jeremydaly/lambda-api 的其他 Issue

查看 jeremydaly/lambda-api 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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