We have built a NextJS website that is running on AWS Amplify, we are currently using getStaticProps in order to render the pages, and we generate them using getStaticPaths.
We would like to use on-demand revalidation in order to refresh the data on our command when we update the database, for example.
Our local env works perfectly, the data is the same until we change and revalidate using our secret API endpoint, on the other hand when we deploy to AWS Amplify, the revalidation doesn't work.
We looked into the logs and didn't see any errors, nor are the permissions for SQS invalid. We even removed the branch and redeployed it, yet nothing worked.
I have tried searching for the same problem online yet didn't find any solution, did anyone here stumble upon the same issue?
Thank you!
Seems like this isn't supported yet, and in the works by the Amplify team.
This was answered in an issue I opened on Amplify's GitHub:
https://github.com/aws-amplify/amplify-hosting/issues/3116
right now, Amplify Hosting does not support on-demand ISR. Supporting
it is on our roadmap and we will update our documentation to make this
clear.
I'm using Vercel while they work on that.
Related
Recently I have been trying to re-boot my app. This includes adding google play services to my app.
I setup a google cloud platform account and then linked it with the developer console for my app.
Next I setup the OAuth consent screen. After completing everything it asked me to verify my website and domain; I completed this step with the google search API.
Despite all of these efforts I still got the error, Pending developer action.
Here is my verified domain (blurred out for obvious reasons):
After observing the documentation a little bit more, it tells me that I must continue/reply to the email thread with their Trust and Safety team, but I have not received any emails from them with my developer email -
Thanks in advance
-James
I have actually found the solution to this problem, and I think I can safely say that this is due to human error every single time.
When linking your google play app in the developer console to google cloud it might automatically create one for you, but if you reload the page it will make a second one. You have to make sure you select the right google cloud app to link because it might not properly connect if you use the wrong one.
Once you have done this you need to create a website or link a website that has been verified (you can verify it yourself) with google. You should then be able to setup your app easily! Not every step will be instant you might sometimes have to wait a day or two for it to work.
I wanna make a flutter web app and deploy it to AWS.
After researching it looks like using AWS Amplify is the easiest way so I try it, however after I successfully deploy it, it only shows a white screen with this showing on the log after I inspect:
However the web app show up just fine on my GitHub page and Codemagic, you can see it on rezyfr.github.io and fl-blog.codemagic.app. And here is my amplify yaml file:
Is anyone ever experience this and found the solution? Or anyone have a better way to deploy flutter web on AWS?
I use Java APIs for the CRUD operations of the google cloud deployment manager API. I can create, preview, delete deployments OK.
But when I try to update an existing deployment that's in preview mode, the API returns the below error.
Deployment in preview must not have a target with UPDATE
The same inputs works OK for create and preview. So, I'm sure that the inputs are OK.
I looked up for others who have reported this issue.
Here is one such report but no solution.
Does anyone know if there's a git hub repo for google cloud deployment manager where we can report this issue?
As mentioned in the answer here, is a known issue and you can still use the workaround suggested.
I have created an issue tracker for this error message. So, you can add your comments there and follow up for upcoming updates.
I am currently fiddling around with AWS CodePipeline for the first time and set up the Source and the Build step so far with a demo project.
I have connected the Source Step with a GitHub account (a system-account we use), with admin access to all Repos. As the documentation states, the OAuth-scopes admin:repo_hook and repo are required for this to use; which are granted and the connection is fine.
As the title of this question already states: The integration works just fine - when I push a new commit on master to GitHub, the Pipeline starts working and runs through smoothly.
My question however is: How? As the docs state here:
To integrate with GitHub, AWS CodePipeline uses OAuth tokens
however, when looking in my GitHub settings, I would have expected to find the application listed as an "OAuth application" directly on the Repository or on the organization "OAuth applications", but neither is the case!
Thus, I am wondering how CodePipeline recognizes my new commit. Is it polling the SCM or some other sort of magic? I did not find any WebHooks either.
Thank you in advance!
AWS CodePipeline is connected to GitHub via the new "Integrations" concept: https://github.com/integrations/aws-codepipeline
This concept was announced here: https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/
GitHub Integrations authenticate using JSON Web Tokens and private/public keys, so I'm not sure if AWS are technically correct in describing that as "OAuth" or not. Details here: https://developer.github.com/early-access/integrations/authentication/#as-an-integration
I have been working on moving our continuous integration(CI) to Azure using Azure's built in CI. After each build, it shows the last commit message as the deployment reason. I would like to put the current version of my App in there.
Does anybody know if there is a way I can override, or extend the information shown in the Deployment details view after a build for Azure WebServices.
I haven't seen anywhere to add this, so I guess UserVoice is the best way to get their attention. I'd certainly vote it up.