-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After removing cloudFront (Hosting endpoint information is not updated). #402
Comments
Thanks for the feedbacks, this is a known issue. |
By the way i think that the command amplify status should be added to the workflow on the documentation to me it's clear that the right process should be :
|
Is there a workaround? Is manually modifying the amplify config files to point at the S3 bucket an acceptable solution? |
@nirvdrum |
correct hosting meta output after CloudFront removal fix aws-amplify#402
fix the hosting output when CloudFront is removed fix aws-amplify#402
fix hosting category output after CloudFront is removed fix aws-amplify#402
fix(#402) hosting category output after CloudFront is removed
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Hi,
After removing cloudfront i noticed that the endpoint information is never updated when i use amplify status command even after making a push or a publish.
even if my amplify publish is uploading the files to the S3 and not to cloudflare it still shows the cloudflare endpoint.
Steps to reproduce the behavior:
this information is false ( i can not relay on the git status to be sure i'm pushing to S3 or to cloudFlare
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: