Make experimental a runtime flag#27223
Conversation
1cf6f42 to
6ed62b5
Compare
integration-cli/check_test.go
Outdated
There was a problem hiding this comment.
nit: IMO the comment should be moved to L267
There was a problem hiding this comment.
Updated, thanks.
bba1b28 to
da64999
Compare
Otherwise design LGTM 👍 |
This is a requirement, but it won't change much about this PR, so I'm moving it to code review so we can try and get it in for 1.13.0. |
|
This seems to be working as expected, code looks fine. LGTM |
|
LGTM |
ec36188 to
f522adf
Compare
hack/make/build-rpm
Outdated
There was a problem hiding this comment.
Shouldn't this block just be removed completely, as in build-deb?
There was a problem hiding this comment.
Should I remove --define '_experimental ${DOCKER_EXPERIMENTAL:-0}' too ?
|
We should have a CI check or label to prevent future PR's from adding an experimental build-flag /cc @ehazlett @mlaventure |
There was a problem hiding this comment.
Were we just never running tests on windows with experimental enabled previously?
There was a problem hiding this comment.
Correct, all the test have DaemonIsLinux as a prerequisite
hack/make/.integration-daemon-start
Outdated
There was a problem hiding this comment.
Aren't the experimental features tested regardless of whether this is set on our integration daemon, or does this mean we'll still need to run the full test suite twice (once without and once with this set)?
There was a problem hiding this comment.
Without it the experimental endpoint are not "exposed" to the clients.
However, if there''s code elsewhere that is supposed to be experimental and isn't guard by the proper check, testing both with and without the flag should help catch it.
f522adf to
71147c5
Compare
|
@thaJeztah @mlaventure should we move this to docs-review or should we do that in a follow up PR? |
|
@docker/core-machine-maintainers machine will need some updates to support the new experimental flag. LGTM |
There was a problem hiding this comment.
Missing "header", I guess?
Every API response now includes a `Docker-Experimental` header specifying if
experimental features are enabled (value can be `true` or `false`).|
Had one small nit on docs, but feel free to go ahead if you prefer |
Signed-off-by: Kenfe-Mickael Laventure <[email protected]>
5d3eebb to
7781a1b
Compare
|
@thaJeztah made the doc change. |
|
all green! |
|
https://github.com/docker/docker/blob/master/experimental/README.md should probably be updated for this change as well, right? |
|
Can you point me to the reference please? I could not see it in docs |
|
docs for 1.13 are not yet published, but the flag itself is documented in the |
|
Is there a reason docs are lagging? I never saw that happening before. |
|
Not all parts of the release are released yet, so the release will be officially announced after all projects have finished their release, and the docs will probably go out together with that. |
|
ok |
Signed-off-by: Kenfe-Mickael Laventure [email protected]
Left to do:
"experimental": trueif fetched fromhttps://experimental.docker.com/See what solution is adopted by API/CLI version mismatch #25498 and piggy back on it to check the daemon experimental flagCloses #26713