generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 175
Closed
Labels
internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Description
Summary
We recently started migrating our developer docs to a new domain and have setup a redirect on the old domain.
In some of the e2e tests for the Tracer utility we make HTTP requests to our docs to test that tracing outgoing requests works.
Now that we've changed the domain and set the permanent redirect, the response code is no longer 200 and so our tests are failing.
We should update the domain in the tests.
Why is this needed?
So that we can continue running e2e tests as normal.
Which area does this relate to?
No response
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Type
Projects
Status
Coming soon