Skip to content

Ability to migrate accounts bеtween domains #7555

Closed as not planned
Closed as not planned

Description

@top-secrett
ISSUE TYPE
  • Feature Idea
COMPONENT NAME
UI
SUMMARY

It would be great if CS has function to migrate accounts and its resourses between different domains.
We created stucture of domains based on some logic. Now we want to change it, but can't do it.

Activity

  1. changed the title [-]Ability to migrate users bеtween domains[/-] [+]Ability to migrate accounts bеtween domains[/+] on May 24, 2023
  2. DaanHoogland commented on May 24, 2023

    @DaanHoogland
    Contributor

    sounds good @top-secrett , between the lines I read that you not just want to move accounts between domains but also subdomains, is that right?

  3. top-secrett commented on May 24, 2023

    @top-secrett
    Author

    @DaanHoogland yeah, you're right. For example, from migrate account form domain VS/subdomain1 to VS/121/subdomain1

  4. DaanHoogland commented on May 25, 2023

    @DaanHoogland
    Contributor

    ok, so not move domain sub1 from /dom1/sub1 to dom2/sub1?
    in any case that may be a different feature and a first step just the account.
    thanks

  5. top-secrett commented on May 25, 2023

    @top-secrett
    Author

    @DaanHoogland I think account moving is more flexible at least in our case. But domain moving (with all accounts inside?) would be great too.

  6. DaanHoogland commented on May 26, 2023

    @DaanHoogland
    Contributor

    @top-secrett initial investigation leads to several issues. A non-exhaustive list:

    1. an account does not have to be unique globally but has to be unique within a domain
    2. usage data for a resource contains account and domain data that will not be consistent anymore after moving an account

    that said, it is a good feature and worth investigating. cc @vishesh92 @rohityadavcloud

  7. JoaoJandre commented on May 26, 2023

    @JoaoJandre
    Contributor

    @DaanHoogland I think account moving is more flexible at least in our case. But domain moving (with all accounts inside?) would be great too.

    @top-secrett PR #7446 adds the feature to move subdomains between domains (with everything that inside them). As @DaanHoogland said, account migration is still a different feature from #7446; however, PR #7446 may be a first step towards account migration.

  8. DaanHoogland commented on May 30, 2023

    @DaanHoogland
    Contributor

    @DaanHoogland I think account moving is more flexible at least in our case. But domain moving (with all accounts inside?) would be great too.

    @top-secrett PR #7446 adds the feature to move subdomains between domains (with everything that inside them). As @DaanHoogland said, account migration is still a different feature from #7446; however, PR #7446 may be a first step towards account migration.

    you are right @JoaoJandre , domain moving is actually easier as it removes the necessity to check for uniqueness of account names. Also usage records remain valid as the account-domain relation stays the same. Let's get your #7446 in before we consider this.

  9. added this to the unplanned milestone on May 30, 2023
  10. github-actions commented on Aug 23, 2026

    @github-actions

    This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

  11. DaanHoogland commented on Aug 25, 2026

    @DaanHoogland
    Contributor

    @JoaoJandre there is already an implementation of moveDomain by now as you implemented in #7446 , should we still keep this open? (moveAccount)

    my objection (.1) from #7555 (comment) can easily be mitigated by throwing some NotAllowedException, but objection (.2), histroic usage remains, So I tend towards closing this as unplanned.

  12. JoaoJandre commented on Aug 25, 2026

    @JoaoJandre
    Contributor

    @JoaoJandre there is already an implementation of moveDomain by now as you implemented in #7446 , should we still keep this open? (moveAccount)

    my objection (.1) from #7555 (comment) can easily be mitigated by throwing some NotAllowedException, but objection (.2), histroic usage remains, So I tend towards closing this as unplanned.

    @DaanHoogland as no one currently seems interested in implementing this. I would close it. It seems a bit too complex to implement and I do not see much gain from it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions