docker / roadmap

Welcome to the Public Roadmap for All Things Docker! We welcome your ideas.
https://github.com/docker/roadmap/projects/1
Creative Commons Zero v1.0 Universal
1.46k stars 246 forks source link

[Docker Hub] Add ability to rename/delete user accounts #44

Open pkennedyr opened 4 years ago

pkennedyr commented 4 years ago

Tell us about your request Users should be able to rename or delete their user accounts.

Which service(s) is this request for? Docker Hub

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? See https://github.com/docker/hub-feedback/issues/11

Are you currently working around the issue? NA

Additional context NA

tianon commented 4 years ago

There are technical reasons why this isn't trivial (renaming repos, etc without a real "redirect" ability for docker pull like what GitHub can do on renames), but perhaps offering to automatically create an organization with the old username (especially if there are repos that would be affected) would be an OK compromise to at least that issue?

(I went to go find the setting to rename a user account today and was surprised to find it didn't exist yet :sweat_smile:)

manishtomar commented 4 years ago

There are technical reasons why this isn't trivial (renaming repos, etc without a real "redirect" ability for docker pull like what GitHub can do on renames),

IMHO this is must have before providing renaming feature.

but perhaps offering to automatically create an organization with the old username (especially if there are repos that would be affected) would be an OK compromise to at least that issue?

@tianon We've convert user to org feature that does this. https://hub.docker.com/support/doc/how-do-i-convert-my-docker-hub-user-account-into-an-organization-account . Did you mean something else?

tianon commented 4 years ago

I think it's related, but I'm suggesting something slightly different. There are benefits a rename could/would provide that converting to an organization would not (such as the semi-new "Pushed by so-and-so" text that appears on tags being updated to the new username), so I'm suggesting that as an intermediate step, this could be implemented without having proper redirects by allowing users to essentially rename-current-user-and-create-an-organization-for-old-username in one step.

Imagine I've got jsmith/foo and jsmith/bar pushed, and the tags page lists that the images were "Pushed by jsmith" but now I want to rename myself to "ksmith" and I want to ensure all the references to my user are updated -- my suggestion is that "rename user jsmith to ksmith + create organization jsmith to keep the existing jsmith repos" could be an intermediate step before redirects are available (and possibly simpler to implement, although I'm not familiar with the data structures of the Hub behind the scenes). :sweat_smile:

In this example, jsmith/foo and jsmith/bar would still exist, and my new "ksmith" user would still be the owner (by virtue of being the owner of the newly created "jsmith" organization), but they would say "Pushed by ksmith" in their tags.

There are also user accounts that don't have any repos of their own and only push to organizations or other users' repos for whom a rename should be much simpler (especially if they don't care about the old username but simply want to update references to their user across the Hub) -- this is the situation that brought me to looking this up in the first place. :sweat_smile:

ao commented 3 years ago

+1 ∞

tianon commented 1 year ago

Just played with Hub's SSO for the first time, and realized that having SSO choose a username for me makes this even more important (IMO). :see_no_evil:

Edit: in case it isn't already obvious, deadnaming is a great example of why this might be problematic (ie, even if the org is happy to change the user's name/display/etc, their Hub username is "stuck") :grimacing:

makidoll commented 1 year ago

I'd like to be able to change to Docker hub username too if it's possible. Can I contact anyone who can help me in the meantime? Thank you

ghost commented 1 year ago

Is the thumbs up enough or should we all post +1 to increase prio? :p

ThibaudMoretto commented 1 year ago

+1

carchobe commented 1 year ago

+1 please

morganh83 commented 1 year ago

+1

fmurodov commented 1 year ago

+1

aastopher commented 1 year ago

+1

daniel-souza commented 1 year ago

+1

jebwatson commented 1 year ago

+1

tomposmiko commented 1 year ago

+1 No redirect needed.

GinoPane commented 1 year ago

+1

ghost commented 1 year ago

+1

ratio-dd commented 1 year ago

+1

tungnguyen17 commented 1 year ago

+1

broot02 commented 1 year ago

+1

mgreen-bishs commented 1 year ago

+1

douglasss commented 1 year ago

+1

Xaypanya commented 1 year ago

+1

DRV2EGR commented 1 year ago

+1

yasinskyi commented 1 year ago

+1

ChoiIseungil commented 1 year ago

+1

manuh-L commented 1 year ago

+1

aurkaxi commented 1 year ago

+1

platput commented 1 year ago

+1

danbrown commented 1 year ago

+1

yavorg commented 1 year ago

+1

LeKSuS-04 commented 1 year ago

+1

robocordyceps commented 1 year ago

+1

acuere commented 1 year ago

+1

abbyhu2000 commented 1 year ago

+1

cyanogenic commented 1 year ago

+1

mirusky commented 1 year ago

+1

They don't even care about it, as time passed and they didn't even commented about it.

IMO, they MUST have this ability and should warn user that changing name could compromise push / pull and they must change all scripts, and warn their own users...

mbani01 commented 1 year ago

+1

thaJeztah commented 1 year ago

Hi! I work at Docker (but not on the Hub team, so bear with me on details :see_no_evil:). I was actually asking about this issue last week (week before? need to check my Slack history) as I wondered if we made progress on this, and I know it’s a feature that comes up frequently.

I found some people that worked on this, and they gave me some details;

The short version:

There has been some progress, but no ETA yet, and some of this depends on services we integrate with.

The slightly longer version:

The team spent some sprints working on this feature; one of the known complications is situations where images also have to be migrated, so their first goal was to fix the “lower hanging fruit”; accounts that have no content (images) in the namespace. They implemented this feature (allow rename, but only if no content is present, otherwise to contact support). This feature was rolled out in a staging environment, but revealed new challenges for cases where single-sign-on integration is enabled; syncing accounts with those services turned out to be, erm, “challenging” :speak_no_evil:. One of the developers on the team became a victim of this, got locked out of their account, and it took literally months (:grimacing:) to have their account reinstated in those services.

So the “good news” is that the work gave us more insight into the scope of this work, and areas that need to be worked. The bad news is that, while we’re in talks with these providers to work on a solution, we don’t have an ETA yet on when this will be sorted.

TL;DR; This feature definitely remains on the backlog (and knowing myself, I’ll probably continue harassing those working on it :innocent: :joy:), but don’t (yet) know “when”.

danbrown commented 1 year ago

Thanks for the information @thaJeztah, I can imagine how complicated this can be as something that was never planned from the beginning (we've been something similar recently 😂)

thaJeztah commented 1 year ago

Yes, with complex, distributed systems, things are rarely "easy". More so, doing without interrupting services (half a billion daily pulls? 😬)

I can imagine how complicated this can be as something that was never planned from the beginning

Big nod.

Fun fact; this ticket was actually created by a former colleague who was Product Manager for Docker Hub. At the time we still had various older systems in service, some of which dated all the way back to "the Docker Index" (the old name of Docker Hub). Those parts were on the roadmap to be replaced "at some point", but also had quite some hard-coded assumptions (who would've thought things could change??), and had to be replaced. The replacement services have been running side-by-side for an extended period of time to verify consistency, and I think we recently were able to decomission the last one of the old services (whoop!).

So, yes, progress has been made, but (per my earlier comment) still lots of "fun" to address.

shcw commented 1 year ago

+1

tyranron commented 1 year ago

This very well complies with the recent announcement of deleting Open Source organizations. So now, any public organization on Docker Hub cannot preserve its images naming without paying. We can create a separate personal account, but we cannot rename it to the former org name once all the images are transferred.

If you have a public org on Docker Hub with public images, you're doomed to:

fguille94 commented 1 year ago

+1

cakesoft-chaitanya commented 1 year ago

+1

joeloliver commented 1 year ago

+1

thaJeztah commented 1 year ago

For those leaving a +1; please use the "thumbs up" emoji on the first comment (as Github allows sorting tickets based on that, and it doesn't send out e-mail notifications to everyone on this thread 😅)

dsdanielpark commented 1 year ago

+1

isaiah-dev-999 commented 1 year ago

+1

3f6a commented 10 months ago

Could we at least have the ability to change username on the forum (https://forums.docker.com) ?