Amplify teams can't share usable PR preview URLs
Teams using AWS Amplify report that pull-request comments link to amplifyapp.com preview URLs even when their apps rely on a custom domain; those default URLs can cause CORS issues or be unusable in their setup. A related request from GitLab users is for merge requests to show preview URLs and build status at all. A configurable notifier could address the sharing gap, but it would not by itself create custom-domain routing or fix CORS.
For development teams using AWS Amplify previews. Mentioned from May 2020 to Jan 2023 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.4/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Feature request: Use custom domain in PR comment for preview link Is your feature request related to a problem? Please describe. When a PR is created, the AWS Amplify GitHub bot comments the preview URL, as added in #264. This is great, except that we are using a custom domain.
Same issue here, everything works fine with our custom domain, except Amplify now adds bogus comment in all our PRs revealing the amplifyapp.com subdomains that were supposed to be hidden, and are not functioning in our use cases
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks