From dfa115290bb8b10077870149485673b59ff5c3d9 Mon Sep 17 00:00:00 2001 From: Andrey Sobolev Date: Tue, 22 Apr 2025 17:13:47 +0300 Subject: [PATCH 1/2] Fix link to Celery docs --- content/manuals/build/building/best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/build/building/best-practices.md b/content/manuals/build/building/best-practices.md index 68ea0de2672b..eb308bcf862a 100644 --- a/content/manuals/build/building/best-practices.md +++ b/content/manuals/build/building/best-practices.md @@ -147,7 +147,7 @@ Limiting each container to one process is a good rule of thumb, but it's not a hard and fast rule. For example, not only can containers be [spawned with an init process](/manuals/engine/containers/multi-service_container.md), some programs might spawn additional processes of their own accord. For -instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker +instance, [Celery](https://docs.celeryq.dev/) can spawn multiple worker processes, and [Apache](https://httpd.apache.org/) can create one process per request. From 0c89cc74132d74f7aa4afd0e859da2109d4bef59 Mon Sep 17 00:00:00 2001 From: Sarah Sanders Date: Tue, 22 Apr 2025 12:16:40 -0400 Subject: [PATCH 2/2] security: remove outdated limitation and add suggestion for OATs (#22461) ## Description - PATs are transferred to org owners when converting a user account to an org now - Adds suggestion to use OATs - Preview: https://deploy-preview-22461--docsdocker.netlify.app/admin/organization/convert-account/ ## Related issues or tickets - [ENGDOCS-2567](https://docker.atlassian.net/browse/ENGDOCS-2567) ## Reviews - [ ] Editorial review [ENGDOCS-2567]: https://docker.atlassian.net/browse/ENGDOCS-2567?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --- content/manuals/admin/organization/convert-account.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/manuals/admin/organization/convert-account.md b/content/manuals/admin/organization/convert-account.md index 00db9570d89f..66791d0396ef 100644 --- a/content/manuals/admin/organization/convert-account.md +++ b/content/manuals/admin/organization/convert-account.md @@ -48,7 +48,13 @@ Consider the following effects of converting your account: - The user account that you add as the first owner will have full administrative access to configure and manage the organization. -- Converting a user account to an organization will delete all of the user's personal access tokens. See [Create an access token](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for steps on creating personal access tokens after converting the user account. +- To transfer a user's personal access tokens (PATs) to your converted organization, +you must designate the user as an organization owner. This will ensure any PATs associated with the user's account are transferred to the organization owner. + +> [!TIP] +> +> To avoid potentially disrupting service of personal access tokens when converting an account or changing ownership, it is recommended to use [organization access tokens](/manuals/security/for-admins/access-tokens.md). Organization access tokens are +associated with an organization, not a single user account. ## Convert an account into an organization