Before we decide, I'd like to propose another view angle. Thanks to the removal of the endpoint aliases, a widely used but only occasionally maintained mesos-dns have been updated and a newer version will be released soon [1] — thanks to jdef. I understand the frustration when software stops working after an update for silly reasons like removing endpoint aliases, but at the same time it can be an incentive to update other components in the ecosystem as well, switching not just from one endpoint to another, but bringing other changes together into the release.
[1] https://github.com/mesosphere/mesos-dns/releases/tag/v0.7.0-rc2 On Fri, May 10, 2019 at 5:03 PM Vinod Kone <vinodk...@apache.org> wrote: > I propose that we revert this change and keep the ".json" endpoints in > master branch and 1.8.x > > My reasoning is that, we have ecosystem components (e.g., mesos-dns which > is yet to have a release with fix) and anecdotally a bunch of custom > tooling at user sites that depend on these ".json" endpoints (esp. > /state.json). The amount of techdebt that we saved or consistency we > achieved in the codebase by doing this is not worth the tradeoff of > breaking some user/tooling, in my opinion. We could revisit this if and > when we do a Mesos 2.0. > > On Wed, Aug 8, 2018 at 9:25 AM Alex Rukletsov <a...@mesosphere.com> wrote: > > > Folks, > > > > The long ago deprecated '*.json' endpoints will be removed in Mesos > 1.7.0. > > Please use their non-'.json' counterparts instead. > > > > Commit: > > > https://github.com/apache/mesos/commit/42551cb5290b7b04101f7d800b4b8fd573e47b91 > > JIRA ticket: https://issues.apache.org/jira/browse/MESOS-4509 > > > > Alex. > > >
