11–17 of 17 posts
I'm not sure what this is for, most people already use GHA without any control plane and deploy just fine.
Putting the obvious facetiousness of this whole endeavor aside, doing something like this would mean that your reliability record is exactly as good as GHA
You misunderstand, this only deploys, has nothing to do with runtime.
I've done this same thing, GHA as a control plane. It was for people who could wait; the actual operators regularly skipped the middleman. Preference or necessity, take your pick.
Earlier quoted context omitted.
You misunderstand, this only deploys, has nothing to do with runtime.
You misunderstand, (continued) runtime is dependent on the ability to deploy. For instance: a vulnerability is realized or a customer needs something (availability, feature, who knows) , you'll appreciate handles under your control. Service can easily degrade, without. I've done this same thing, GHA as a control plane. It was for people who could wait; the actual operators regularly skipped the middleman. Preference…
Earlier quoted context omitted.
You misunderstand, (continued) runtime is dependent on the ability to deploy. For instance: a vulnerability is realized or a customer needs something (availability, feature, who knows) , you'll appreciate handles under your control. Service can easily degrade, without. I've done this same thing, GHA as a control plane. It was for people who could wait; the actual operators regularly skipped the middleman. Preference…
Runtime is separate from deployment. An incident in your deployment infra doesn't affect production. The fact that you may have to deploy to change what's live is what defines it as an incident, but it's still a different thing from a production incident.
Deployment is how you fix problems with the runtime. Not just availability, shortcomings. I'm not going back and forth about this, there is a relationship here. Man architects, God laughs.
Here's a fun phrase to latch onto: 'escape', production is the test environment we all share.
GitHub goes down, yes, your service remains. For now. We chose to not wait, suggest others don't either. I agree in spirit with the GP. Misfortune is the fortune that never misses.
Their nines aren't yours, you bet.
Earlier quoted context omitted.
Runtime is separate from deployment. An incident in your deployment infra doesn't affect production. The fact that you may have to deploy to change what's live is what defines it as an incident, but it's still a different thing from a production incident.
From "nothing to do with" to "separate", I'd say we're making progress. Deployment is how you fix problems with the runtime. Not just availability, shortcomings. I'm not going back and forth about this, there is a relationship here. Man architects, God laughs. Here's a fun phrase to latch onto: 'escape', production is the test environment we all share. GitHub goes down, yes, your service remains. For now. We chose to…