fix(pricing): update pricing API endpoint and guard non-OK responses - #2283
Merged
pedro-ribeiro-azion merged 1 commit intoJul 23, 2026
Merged
Conversation
The previous endpoint (www.azion.com/api/pricing) now returns an HTML 404 page, crashing the build with a JSON parse error. Point the fetch at the working edge application host and fail with a clear error when the API responds with a non-2xx status.
souzavinny
requested review from
egermano,
isaquebock and
pedro-ribeiro-azion
as code owners
July 22, 2026 23:38
egermano
approved these changes
Jul 23, 2026
pedro-ribeiro-azion
approved these changes
Jul 23, 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.
Brief
Production builds were failing on the pricing pages: the API at
www.azion.com/api/pricingnow returns an HTML 404 page instead of JSON, crashingTablePricing.astroat build time. Fixed by reverting the component at the working endpoint from previous state and adding aresponse.okguard so future API failures produce a clear build error.Activities
fetchPricingData()insrc/components/Table/TablePricing.astroand confirmed the new endpoint returns HTML 404 for every product slug.https://vef4esszhdq.map.azionedge.net/api/pricing/get/product_slug/<slug>(Verified on the commit history at Fix/empty table loading #2060) and added aresponse.okguard.Evidences
product_slug/metric_slugpairs used in the EN/PT-BR pages have matching data. All prices there are the same as the one currently live.Before:
After:
