I have several user code deployments that happen to each have an asset with the same name. I am seeing a warning:

Multiple asset definitions found

for these asset groups. It seems that we cannot have assets with the same names in different deployments, but I was wondering if this is expected behavior or a bug? It seems like we should be able to have assets with the same names as long as they are in separate asset groups.

The asset groups lay things out in the Overview navigation tree on the left, but don't affect this side of things. To avoid name conflicts, try the asset_prefix. I usually set it to be the same as the asset_group. This will put your assets into folders when you look at them in /assets.

Thanks @Chris Comeau! Looking into this.