Porter is looking to improve dependency management per this proposal and a key part of the implementation is that installations can be scoped by namespace and queryable by a set of labels.
I will follow up this issue with a PR to both the Claims and Credential Set specs to includes these concepts. For dependency management, I think we just need this for claim data but it's going to be useful for all CNAB tool data. For example, being able to have an installation reference a credential set that is in the same namespace.
Looking at cnab-spec's crud interfaces and types, we can generalize the "group" argument that allows us to do foreign key references and change it to a map[string]string to support labels. Since namespace needs to be understood by the storage providers in order to create unique keys, namespace should be added as an argument to any functions that accept a name.
Porter is looking to improve dependency management per this proposal and a key part of the implementation is that installations can be scoped by namespace and queryable by a set of labels.
I will follow up this issue with a PR to both the Claims and Credential Set specs to includes these concepts. For dependency management, I think we just need this for claim data but it's going to be useful for all CNAB tool data. For example, being able to have an installation reference a credential set that is in the same namespace.
Looking at cnab-spec's crud interfaces and types, we can generalize the "group" argument that allows us to do foreign key references and change it to a map[string]string to support labels. Since namespace needs to be understood by the storage providers in order to create unique keys, namespace should be added as an argument to any functions that accept a name.