Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support moving cross-site collection with spo folder copy #6310

Closed
milanholemans opened this issue Sep 4, 2024 · 2 comments
Closed

Support moving cross-site collection with spo folder copy #6310

milanholemans opened this issue Sep 4, 2024 · 2 comments

Comments

@milanholemans
Copy link
Contributor

milanholemans commented Sep 4, 2024

This issue is related to:

However, spo folder copy uses the same endpoint that causes problems with the commands mentioned above, for some reason, there are no limitations for the copying of folders. However, I think it's good to keep these 4 commands aligned and let them use the same endpoint so they behave the same. Additionally, with the current endpoint, it is impossible to know the name of the new copied folder when using --nameConflictBehavior rename. With the new endpoint, this is possible.

@milanholemans
Copy link
Contributor Author

Will work on it when #6390 has been merged. All changes made in the spo util are needed for this issue as well.

@MathijsVerbeeck
Copy link
Contributor

@milanholemans They have been merged.

milanholemans added a commit to milanholemans/cli-microsoft365 that referenced this issue Oct 18, 2024
milanholemans added a commit to milanholemans/cli-microsoft365 that referenced this issue Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants