Remove deprecated cli flags#17724
Conversation
|
nice clean-up! |
|
I did want to take care of https://github.com/docker/docker/blob/master/docs/misc/deprecated.md#docker-content-trust-env-passphrase-variables-name-change as well but it's weird it was deprecated in 1.9 and target for removal is 1.10 |
|
Darn! So had this on my to-do list, thought this would be an easy one for me to pick up, LOL |
|
There are all the tests yet to be fixed if you want to carry this lol O:) |
|
hehe. no, feel free to take it! 😺 |
577afbf to
cfb1957
Compare
a85a059 to
514af47
Compare
514af47 to
f484eb9
Compare
|
Windows fail seems related |
|
ping @jhowardmsft I can't seem to find the issue with windows :/ |
|
@runcom You need to kick it off again. See my IRc log from Friday evening. You've hit a common CI problem. |
|
@jhowardmsft oh :( thanks for looking! |
There was a problem hiding this comment.
was --no-trunc deprecated? I don't see it in the deprecated doc file.
There was a problem hiding this comment.
it's in the file https://github.com/docker/docker/pull/17724/files#diff-9207f9a977bc11e99cfb49522dd26292R30 a line below
There was a problem hiding this comment.
But was it listed in the deprecation docs? If not, and we still want to delete it anyway, then let's add it.
There was a problem hiding this comment.
-notrunc was deprecated and I removed it
--no-trunc in docker search wasn't deprecated and I kept it in https://github.com/docker/docker/pull/17724/files#diff-9207f9a977bc11e99cfb49522dd26292R30
why do we want to delete even --no-trunc if it wasn't listed?
There was a problem hiding this comment.
Oh sorry, I misread the above line - I thought you were removing it - I missed that its down below on line 30. I was used to seeing git-diff showing just the deleted words.
|
I might be misreading stuff, but the docs talk about |
|
actually, I take that back. There is a |
There was a problem hiding this comment.
I don't think -net is deprecated so I think this test is still valid, no?
There was a problem hiding this comment.
I should remove from here https://github.com/docker/docker/pull/17724/files#diff-0189e098e6ba3aeffd9ee321ee6aca8aL168
There was a problem hiding this comment.
I'm not following. Is --net/-n deprecated? I not then shouldn't this entire testcase be kept?
There was a problem hiding this comment.
I'm a little concerned from the Windows side if --net=none is deprecated? What's the replacement? There will be other plumbing required in the Windows drivers if it is deprecated (along with this test)
There was a problem hiding this comment.
There was a problem hiding this comment.
-n and --networking are deprecated, nothing to do with --net
The first part of the test is testing --net so it should be kept, the other -n -- I'll remove it
f484eb9 to
06a8511
Compare
|
needs rebase |
06a8511 to
475e5a7
Compare
|
@tiborvass updated & rebased |
|
@runcom I'm just going to leave this here: http://stackoverflow.com/questions/9208091/the-difference-between-deprecated-depreciated-and-obsolete. I'm assuming that we want to make these "obsolete", rather than "decrease their monetary value". Please excuse my pedantry. :) |
|
@stevvooe ahahah I even wrote the commit message right, excuse my typo as I'm an ESL actually :) |
|
Ok, gave up on windows. |
|
@runcom sorry, needs a rebase :'( |
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
475e5a7 to
7929888
Compare
|
LGTM |
The old command line options have been deprecated in 1.8.0 and eventually removed in 1.10.0 through PR moby#17724, though the deprecated.md still shows `Target For Removal In Release`. This fix updates the deprecated.md and changes `Target For Removal In Release` to `Removed In Release`. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
As per https://github.com/docker/docker/blob/master/docs/misc/deprecated.md#old-command-line-options
Signed-off-by: Antonio Murdaca runcom@redhat.com