Change parent

[Flix6x]

I wonder if the PATCH endpoint should allow setting the parent ID - i.e. can parents change in the lifetime of an asset?

I think that would be handy for editing a site's asset structure, yes. Separate issue, though, imo. Otherwise still testing/evaluating?

I would advise probably not, unless you see a reason.

This would allow account admins to update their old sites to a more hierarchical representation. What would be a reason to not support it?

Or maybe only in the CLI?

CLI makes sense, too.

If not, then partial_asset_schema should probably also exclude parent_asset_id.

Is this a suggestion for a new PR or in scope of this one, too?

Originally posted by @nhoening and @Flix6x in #1533 (comment)

Two options:

• only setting a parent where there was None
• also changing a parent

Are there good reasons for both?

I feel both are needed to support editing hierarchies, as well as a third option: removing a parent (orphaning).

Originally posted by @nhoening and @Flix6x in #1533 (comment)

[nhoening]

Seems we did this.

• [PR #1773](Feat/change parenthood #1773) added CLI support for assigning, changing, bulk-reassigning, and removing parents.
• [Issue #1441](Edit asset: set parent ID #1441), which asks essentially the same question, was closed by [PR #1957](feat: allow update of parent asset on UI #1957). That PR added UI parent editing and same-organisation validation to PATCH.
• Current PATCH code supports all three transitions: no parent → parent, parent A → parent B, and parent → null.