This also explains why the best engineers are also the best at admitting what they don't know. Which is something we have worked into our interviews - amazing how easy it is to spot a poor engineer by asking what their latest failure was.
Once the number three, being the third number, be reached, then lobbest thou thy Holy Hand Grenade of Antioch towards thy foe, who, being naughty in My sight, shall snuff it.
My take was that it is not useful, definitely, categorically not useful. It is a potential security hazard though. Especially for 'exploring' self-hosted runners.
We deploy on K8s in OpenStack from a scheduled GitHub Actions pipeline which aggregates DAGs into a new container build based on hashes of hashes. This works well with almost no intervention.
WRT your 1, above any DAG output to stdout/err is available via the logs tab from the graph view of the individual tasks. Almost all our DAGs leverage on the PythonOperator though, not sure if that standardises this for us and your experience is muddied by more complexity than we currently have?
WRT 2. we generate an uber requirements.txt running pyreqs from the pipeline and install everything in the container automatically. Again no issues currently - although we do need to manually add the installation of test libraries to the pipeline job as for some reason auto-discovery is flakier for unit-tests frameworks.
I'm going down to Cowtown, cow's a friend to me
Lives beneath the ocean so that's where I will be
Beneath the waves, the waves, that's where I will be
I'm gonna see the cow beneath the Sea
from memory, listening on loop as a teenager 35 years ago!
Not sure if sarcastic or not. I think most people don’t think of a URL as an address in the way that a building has an address with a strict hierarchy of meaningful parts. I think people think of it more as an atomic long string of characters that the person who made the site labeled it with just by being the first to claim a certain URL.
reply