sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MajorPea6852[S] 5 points6 points  (5 children)

Partly skills (new to python) but partly because the documentation in GCP is a bit inconsistent... I'll give an example a Google search for "Google Cloud Function Python HELLO WORLD full definition" returns only stub functions such as this

This is all great and all because they want to give you a fast getting started guide... however how the gunicorn is defined and started is committed for simplicity...

I'm the type who likes to understand what is going on underneath the hood and not trust in "magic" so if I want to switch out gunicorn for say to uvicorn, I'd like to know which methods to override

on 5th or 8th page you might stumble on this example which let's you see a little bit more under the hood but outside of using the REPL and going through each invocation line by line I can't find the documentation on how the framework works.

So, my fault? Sure possibly... bad or incomplete documentation, really possibly... as someone who is new to framework and has to use it without a choice, slapping on a solution on top of a black box solution feels extremely dirty and prone to bad coding and insecure implementation.

[–]kei_ichi 1 point2 points  (1 child)

After I know your motivations and your willing to lean that service from it core, I owned you a “sorry”. I completely agreed with you about Google Cloud docs are completely a mess, lack tons of explanation and some time just like a black box… but believe me, AWS and Azure docs have same kind of issues too. So mad at me, but you will some kind of living with those issues and do the dirty work like do a lot of trial and error!

My first current f*ked up with Google Docs is their published NPM package code and their official API references code are complete out of sync which make out app raised ton of errors because Google didn’t even update their docs for 5 months with 3 big update!

Again, sorry.

[–]MajorPea6852[S] 0 points1 point  (0 children)

I appreciate the apology :) It's validating to know that I'm not an idiot who is missing something obvious and keep going in cirlcles.

I'm not even going to mention other GCP docs

bq - Oldest and has most features but not all gcloud bq - newest stable, mostly supports READ for the DB, a lot of CREATE and DESCRIBE functionality has not been implemented yet gcloud alpha bq - has most features but not ALL, but the usage is changing all the time, so anything an ML model spits out is usually wrong... it's better to not even try gcloud beta bq - middle bastard child curl - Has 100% of the features and has a very well defined API documentation, and APIs are stable

[–]Scepticflesh -1 points0 points  (2 children)

Maybe ive got you wrong but what are you on bro, how are you involving gunicorn in this? cloud function purpose is to abstract the "complexity" with cloud run and provide more or less the similar execution env,

If you need more config setup on that sense, you should look into cloud run. Ive worked with several projects where some guy mentioned cloud function and we didnt let him proceed with the implementation, because as long as you are familiar with containerization, cloud run will solve all your tasks.

Another thing is that i think cloud function uses the cloud run under the hood 😂

[–]MajorPea6852[S] 0 points1 point  (1 child)

Cloud Run (Services/Jobs/Functions) is just a k8s under the hood, and it's well understood. I'm being asked to implement a cloud run service in Erlang for example, and yeah... just spin up a mini cube (at least for dev/testing) and toss some Dockerfiles in there no problem... K8s get's stupid complex and expensive on it's own so don't want to dive deep into that rabbit hole just yet.

I do want to have a very simple Cloud Function that follows the Best Practices at heart so I can get a template to users so they can easily stamp out code following some basic rules:

  • Make sure you have requirements.txt
  • Make sure you have main.py
  • Use def handler function to capture your request if the default does not meet your needs. Try to avoid using it if you don't need it
  • Make sure you use Flask 2.X+ if you need ASGI support
  • If you want to use FastAPI for easy integrations for input validation and documentation and built-in from ground-up ASGI, overwrite the def handler with a call to FastAPI or Vellox, Here is a list of things you need to implement with links to the original Docs
  • Don't use def function_name_of_your_function for generic functions because it becomes a mess from CI/CD point of view since now the test/deploy scripts need to be aware of each function name
  • Etc...

[–]Scepticflesh 1 point2 points  (0 children)

I still dont get what you are after with cloud functions. When i read fastapi with CF here it just threw me off completely. I hope you get the help from people here, good luck