From aebd0eb3376541642a6122bb7d9faa6ca618a142 Mon Sep 17 00:00:00 2001 From: Markus Raab Date: Mon, 9 Nov 2020 11:24:51 +0100 Subject: [PATCH] decisions: clarify arbitrary metadata --- doc/decisions/arbitrary_metadata.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/decisions/arbitrary_metadata.md b/doc/decisions/arbitrary_metadata.md index 337665357cb..d2250292554 100644 --- a/doc/decisions/arbitrary_metadata.md +++ b/doc/decisions/arbitrary_metadata.md @@ -23,7 +23,12 @@ metadata from `spec:` might end up in `user:`. ## Decision -Do not store metadata in any namespace but spec. +Do not store arbitrary metadata in any namespace but spec but only metadata that is handled by the `spec` plugin. +E.g. for `array`, metadata might be stored in any namespace but this does not present a problem: + +- either the storage plugin does not support arrays, then the metadata will be discarded +- if the storage plugin supports arrays, the data will be serialized as array + (even if the metadata comes from `spec`) Use different storage plugins, or plugins with different configurations, for the `spec` namespace: