[cli] fix domains access permission issues #11446
Draft
+55
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also related: https://github.com/vercel/api/pull/27464
After the Hobby plan migration, several CLI commands stopped working for migrated users due to domains access check.
The main issue is, after the migration, we basically kept all domain resources (Apex zones, the account-level domains) under a personal account and created a new Hobby team, where all other resources (e.g., projects) were moved over. So, those domains are technically under a different account than their new Hobby team, and hence, access/permission checks started failing.
To work around it, currently, users need to explicitly move domains from their personal account to their Hobby team, which is considered to be a breaking change in UX.
To maintain the backward compatibility of this workflow, this PR adds fallback logic to fetch domains from personal account.