Please add Label functionality to the Cypher

[Nunnemann]

We are about to use Labels with unique IDs for all components (here: Instance Type, Layout, Node Type, Task, Workflow, Input, …) of a certain service. This is one way to identify every single component belonging to that ID (aka service) from every UI view and to group several components which make up the service. This is also one way to oversee everything at all and to bring single components in a relation.

Unfortunately Cypher components cannot be labeled and therefore the relation between a secret and a Task or a Spec Template cannot be found out easily. We sometimes need to look through thousand of lines of code to see where secrets have been referenced. Hence, we miss the Label for Cypher components to complete a full service description in our environment in a reasonable way.

We are aware that the Cypher is not planned for export/import and contains sensible data. But we would like to use Labels outside the export/ import functionality and do not see our security in question with additional Labels.

So please add Label functionality to the Cypher.

[tyboyd]

I believe you meant for this to be put in as an idea.

I will always support adding labels to more items in Morpheus. However, I wanted to point out that cyphers might already offer a solution. With cyphers, you can create a custom path, such as ‘secret/your_label/name’ or ‘secret/project_name/label_name/name’. I do still see the value in having labels on cyphers but I think making a logical path can be the solution in most cases.

[Nunnemann]

I also see the path as a good solution, but also somehow different from a label. Therefore, do you recommend to place the topic again as an idea?

We use paths already with our Git repositories and Tasks, and also with secrets. But then, we cannot add a second or third information easily - like when we share the Task or secret with more services.

In case of our secrets, it might be that we would like to put additional information via labels - like renewal information to short living tokens. These ones should be easily searchable.

With labels, we can search from a drop-down and see different categories of information. While using names and paths, we need to search on our own …