-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Rename graph drivers to storage drivers #22228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b50f38f to
f49deef
Compare
|
Hum I seem to have broken the integration-cli tests for experimental storage drivers. I'll investigate that next week: |
|
ping @samoht have you had time to look into those failing tests? |
|
I plan to look at that again in the following days. Do you think that renaming is worth continuing? |
|
Hm, not sure, I know @tiborvass proposed doing so in the past, but not sure if it's really important (well, it's more consistent probably) |
|
ok, so I'll rebase and see what I can do with the failing tests. |
|
ok! We discussed this, and we like it, so moving to code review. Would be nice if we could give the graph driver plugin maintainers a notice :) |
77c3f88 to
c768b24
Compare
|
ping @kolyshkin |
a03d204 to
1561a8f
Compare
|
I think I've fixed the Normally, all my changes are not visible from the user, apart the changes to the experimental storage driver plugins. The remaining bits where
I don't plan to change theses. Next step for me is to update docker/go-plugins-helpers#42 |
|
LGTM |
|
A interesting new error for For TP5, I'm not sure where this comes from... |
|
LGTM |
This is already the case in most of the CLI. This PR updates the codebase to be more consistent. This should not change anything for the user. Signed-off-by: Thomas Gazagnaire <[email protected]>
This is already the case in most of the CLI. This PR updates the codebase to be more consistent. This should not change anything for the user. Signed-off-by: Thomas Gazagnaire <[email protected]>
Signed-off-by: Thomas Gazagnaire <[email protected]>
Signed-off-by: Thomas Gazagnaire <[email protected]>
Signed-off-by: Thomas Gazagnaire <[email protected]>
This is to keep consistent with the name that we are using in the documentation, where "storage drivers" is prefered over the now deprecated "graph drivers" terminology. Signed-off-by: Thomas Gazagnaire <[email protected]>
Signed-off-by: Thomas Gazagnaire <[email protected]>
This match with what the documentation for `--graph` says. Signed-off-by: Thomas Gazagnaire <[email protected]>
Signed-off-by: Thomas Gazagnaire <[email protected]>
|
Rebased on master, and got new funky errors (yay): |
|
Still an issue with TP5: Is that something expected? |
|
Restarted the Windows build, doesn't look like its related |
|
oh boy; this needs a rebase now |
|
let me close this for now, because it's carried in #23237, but we still need to figure out the Windows issue 😢 |
- What I did
I've renamed the occurrences of
GraphDriverbyStorageDriverin the code base to be more consistent with the docs.The only externally-visible change of that PR is a direct API translation of the experimental storage driver plugins API
- How I did it
I've renamed things via grep/replace but I tried to do that carefully, so variable names and comments are also kept consistent.
- How to verify it
I've run
makeandmake testand it seems to work. I need to update docker/go-plugins-helpers#42 to use the new StorageDriver naming scheme, I'll do that once/if that PR is merged.I've tried to run the integration tests for the CLI. The experimental storage driver plugins seem broken (see below).
- A picture of a cute animal (not mandatory but encouraged)