| 2017-03-27 02:41:52 |
Michi Henning |
description |
Looking through the mcloud provider code, it looks like the provider adds additional metadata entries (which is fine). But these do not have any namespace. If we end up adding a well-known metadata item that happens to have the same name as a provider-specific one, we can end up with clashes (such as our version of the item having a different type).
The mcloud provider should prefix all its provider-specific metadata, that is, use "mcloud:suffix" and "mcloud:thumbnail_url", instead of "suffix" and "thumbnail_url". |
Looking through the mcloud provider code, it the provider adds mcloud-specific metadata entries (which is fine). But these do not have any namespace. If we (in the framework) add a new well-known metadata item that happens to have the same name as a provider-specific one, we can end up with clashes (such as the framework version of the item having a different type).
The mcloud provider should prefix all its provider-specific metadata, that is, use "mcloud:suffix" and "mcloud:thumbnail_url", instead of "suffix" and "thumbnail_url". |
|
