JwtSecret removed from ConfigMap when applying the configuration on Helm

[ljupcovangelski]

Describe the bug

When the Airy Core instance is installed with Helm, one creates his own airy.yaml file, as it is not generated automatically. If only allowedOrigins and systemToken are added to the security section of the airy.yaml file, when one runs airy config apply, the generated jwtSecret will be removed from the ConfigMap and that will disable the authentication.

To Reproduce

Steps to reproduce the behavior:

1. helm install airy airy/airy --timeout 10m --namespace airy --create-namespace
2. Create own airy.yaml file with only the allowedOrigins and the systemToken
3. Run airy config apply

Expected behavior

The generated jwtSecret should not be removed from the security ConfigMap.

Screenshots

/

Environment

All

Additional context

Alternatively we can ammend the documentation in the security page and write that the jwtSecret parameter is mandatory if the systemToken parameter is specified.