You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I like the overall train of thought, but I have two issues with the conclusions to this thread: 1. server-side apply will never be sufficient, as it's only a small portion of the overall lifecycle. We will always need to describe our config before and after pushed to the server.
What Apply enables is merging of user-specified declarative intent in VCS and runtime automation: defaults, built-in and third-party synchronous mutating admission control, built-in and third-party asynchronous controllers, autoscalers, continuous deployment systems, whatever.
Yep, agreed we need to merge those runtime inputs sensibly. Just saying that server-side apply is not a substitute for client-side config management tools/workflow. It seemed to me that your OP was suggesting this was so.
borgcfg was a hammer applied to many operational nails for several years: rollouts, scaling, common abstractions, environmental customization, programmatically generated patterns, application configuration, version management, etc. I believe in using the best tool for the job
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
