kayx23 commented on code in PR #13336: URL: https://github.com/apache/apisix/pull/13336#discussion_r3212840373
########## docs/en/latest/plugins/aws-lambda.md: ########## @@ -200,46 +477,186 @@ Next, select **Create resource** to create a sub-path: Enter the sub-path information and complete creation: - +<div style={{textAlign: 'center'}}> +<img + src="https://static.api7.ai/uploads/2024/04/26/7t1yiWjl_create-resource-2.png" + alt="complete resource creation" + width="70%" +/> +</div> Once redirected back to the main gateway console, you should see the newly created path. Select **Create method** to configure HTTP methods for the path and the associated action:  Select the allowed HTTP method in the dropdown. For the purpose of demonstration, this example continues to use the same Lambda function as the triggered action when the path is requested: - +<div style={{textAlign: 'center'}}> +<img + src="https://static.api7.ai/uploads/2024/04/26/vni7yS2q_create%20method%202.png" + alt="create method and lambda function" + width="70%" +/> Review Comment: The new sub-path walkthrough still only matches `/aws-lambda` in the ADC, Gateway API, and APISIX CRD examples, but the verification step sends `GET /aws-lambda/api7-docs`. That request will never hit those routes as written, so the example is broken outside the Admin API tab. These variants need a prefix/wildcard match (for example `/aws-lambda/*` or the equivalent controller syntax) to actually demonstrate sub-path forwarding. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
