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: it should be possible to have different routes and function names. #78

Closed
tripodsan opened this issue Jan 23, 2021 · 1 comment · Fixed by #84
Closed

AWS: it should be possible to have different routes and function names. #78

tripodsan opened this issue Jan 23, 2021 · 1 comment · Fixed by #84
Labels

Comments

@tripodsan
Copy link
Contributor

eg for helix pages, it would be better to have an action helix-pages--html:3.4.1 and have a route helix-pages/pages_3.4.1/html. this will make it easier to select the function alias via the helix-deploy-proxy.

github-actions bot pushed a commit that referenced this issue Jan 26, 2021
# [3.0.0](v2.0.0...v3.0.0) (2021-01-26)

### Bug Fixes

* **deps:** update dependency @adobe/helix-fetch to v2 ([#82](#82)) ([4c91c73](4c91c73))
* **test:** fix failing test ([7f13b39](7f13b39))

### Features

* **aws:** add possibility to define lambda name format ([#84](#84)) ([4404874](4404874)), closes [#78](#78)

### BREAKING CHANGES

* **deps:** minimum node version is now 12
@github-actions
Copy link

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant