NGINXaaS: update cost estimator to use region-based tier mapping and …#1837
Merged
kafeelhasan merged 4 commits intomainfrom Apr 10, 2026
Merged
NGINXaaS: update cost estimator to use region-based tier mapping and …#1837kafeelhasan merged 4 commits intomainfrom
kafeelhasan merged 4 commits intomainfrom
Conversation
…fixed monthly hours
github-actions
bot
added
the
documentation
kafeelhasan
requested review from
bheftel and
xynicole
and removed request for
a team
✅ Deploy Preview will be available once build job completes!
|
bheftel
approved these changes
Apr 8, 2026
LukeBillington
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
NGINXaaS: update cost estimator to use region-based tier mapping and fixed monthly hours
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩