Introduction So this blog post exists mostly as a reminder of what I need to do if I ever need to setup OAuth again with an application since the discovery, trial and error, endless googling, stack overflow articles and countless other blogposts which didn’t really answer the questions I needed answers to get the solution to work.
A pattern I’ve come across often in web development is to make some kind of API call, do something with it (or do nothing!) and return it to the user. Many developers use this pattern with tools like fetch from the native JavaScript library or third parties like Axios. This is mostly fine, until something goes wrong, and then your application behaves in a way that you might not expect.
Cloud Deploy and GKE Autopilot are two relatively new releases from GCP in the DevOps space, tackling two different, but related problems. Both seek to make it easier to get your code running in the cloud and take away much of the complexity of doing it by hand using a bunch of known and well-trodden experiences by many to create a solution which is a starting point that can easily be adopted into something more complex should your workloads require it.
As security practices in software teams are increasingly shifting left, there’s been a trend for developers to get involved in the security of their applications. The most popular way to develop, build, test and run applications in modern software lifecycles is through the use of containers, of which Docker has made hugely popular, especially with orchestration tools like kubernetes becoming prolific in the container workload space.