Add attributes "name" and "group" to Asset class

[Lee-W]

Description

The Asset Class

Use case/motivation

Rationale

Related issues

#42307

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[uranusjr]

First PR published on the database end. #42407

[uranusjr]

Database changes are done. Next I’m going to add the two arguments to the public-facing Asset class so the user can pass them to be stored in the database.

There’s one thing we need to address in the database after we do the above. Since we want to keep history in the asset table, we need to have the unique constraint on (name, uri) so a name can be reused by different assets as long as the URIs are different, vice versa. But we still want only one active asset to use that name. So I’ll add a separate table to only keep track of active (non-orphaned) assets so we can add all those unique constraints appropriately.

[uranusjr]

PR to add database-level uniqu constraint (see previous message)
#42612

(Draft) Main change to add name and group to Asset (tests tbd)
#42812

(Draft) Tweak AssetAlias to match Asset (not strictly a part of AIP-73 but should be a good thing)
#42814

[uranusjr]

Both name and group have been added to Asset, and they are stored on AssetModel.

#42814 is a related PR to also add group to AssetAlias, and change name constraints to match Asset, but not a strict blocker.

[uranusjr]

I think we’re done here!