You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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.
@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.
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.
@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.
@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.
Activity
[-]Ability to migrate users bеtween domains[/-][+]Ability to migrate accounts bеtween domains[/+]DaanHoogland commentedon May 24, 2023
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?
top-secrett commentedon May 24, 2023
@DaanHoogland yeah, you're right. For example, from migrate account form domain VS/subdomain1 to VS/121/subdomain1
DaanHoogland commentedon May 25, 2023
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
top-secrett commentedon May 25, 2023
@DaanHoogland I think account moving is more flexible at least in our case. But domain moving (with all accounts inside?) would be great too.
DaanHoogland commentedon May 26, 2023
@top-secrett initial investigation leads to several issues. A non-exhaustive list:
that said, it is a good feature and worth investigating. cc @vishesh92 @rohityadavcloud
JoaoJandre commentedon May 26, 2023
@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.
DaanHoogland commentedon May 30, 2023
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.
github-actions commentedon Aug 23, 2026
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.
DaanHoogland commentedon Aug 25, 2026
@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.
JoaoJandre commentedon Aug 25, 2026
@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.