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.

Sign up for GitHub

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

Jump to bottom

Add prices for additional regions #15

Closed
janritter opened this issue Sep 5, 2022 · 1 comment
Closed

Add prices for additional regions #15

janritter opened this issue Sep 5, 2022 · 1 comment
Labels
enhancement New feature or request released

Comments

@janritter
Copy link
Owner

Currently prices are always calculated for eu-central-1.
Goal of this issue is to support price calculation for all other regions as well based on the region from the ARN.
@janritter janritter added the enhancement New feature or request label Sep 5, 2022
janritter added a commit that referenced this issue Sep 10, 2022
@janritter
chore(#15): added script to get lambda duration pricing per region
91218c6
janritter added a commit that referenced this issue Sep 10, 2022
@janritter
Merge pull request #22 from janritter/feat/#15/multi-region-price-sup…
b9abec8 
…port

Multi region price support
janritter pushed a commit that referenced this issue Sep 10, 2022
@semantic-release-bot
chore(release): 1.0.0 [skip ci]
c6ae37b 
# [1.0.0](0.5.0...1.0.0) (2022-09-10)

### Bug Fixes

* **deps:** updated aws-sdk ([9b9b325](9b9b325))

### Features

* **#15:** added price support for all AWS regions - resolves [#15](#15) ([00575a4](00575a4))
@janritter
Copy link
Owner Author

janritter commented Sep 10, 2022 •
edited
Loading

🎉 This issue has been resolved in version 0.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@janritter