4 ms·
I've had APIs subtly break on me between at least 2 releases (I think it's actually 3, but one time may have been user error). The main culprits were changing t
by jpallen 11y ago
I've had APIs subtly break on me between at least 2 releases (I think it's actually 3, but one time may have been user error). The main culprits were changing the parameters which are passed on container creation vs on container start, and changing error messages/response codes.
- cpuguy83 11y agoYes, we have changed response codes when the old ones were just wrong. Like returning a 500 when really it should be a 404, that kind of stuff. As far as start/create params, these should not be changed at all, other than that you can pass the options that you could one only pass on start to create. If something has broken here, it was most likely a mistake and should be reported on GH. Even if we change the underlying configuration, we do version the API and make sure we are sending/receiving the same structs over the wire. TLDR; if something broke in the API, please report.