SITES-41950: add experimental prefix fallback for AEM Content API resolve and edit URL calls#1527
Open
SITES-41950: add experimental prefix fallback for AEM Content API resolve and edit URL calls#1527
Conversation
…olve and edit URL calls Try experimental API prefix first (CONTENT_API_EXPERIMENTAL_PREFIX / PSS_API_EXPERIMENTAL_PREFIX), then fall back to the standard prefix if the experimental endpoint returns a non-200 or a network error. Updates both determineAEMCSPageId and getPageEditUrl.
terinmez
force-pushed
the
wip-switch-capi-endpoint
branch
from
0751114 to
0e382cc
Compare
|
This PR will trigger a minor release when merged. |
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
1 participant
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.
With the introduction of the aem.adobe.experimental scopes, the API-Router will permit access to experimental endpoints only if they are properly addressed. Today it was possible to use the future production endpoint, e.g. /adobe/pages instead of /adobe/experimental/aspm-expires-20251231/pages .
We need to make sure in the Codebases that they use the proper experimental paths.
Try experimental API prefix first (CONTENT_API_EXPERIMENTAL_PREFIX / PSS_API_EXPERIMENTAL_PREFIX), then fall back to the standard prefix if the experimental endpoint returns a non-200 or a network error. Updates both determineAEMCSPageId and getPageEditUrl.
Please ensure your pull request adheres to the following guidelines:
Related Issues
https://jira.corp.adobe.com/browse/SITES-41950
Thanks for contributing!