# Bug ## Description I have been running bb for some time using the quickstart shell script; meaning i just ran helm upgrade from a (local) clone of the bb upstream. This worked fine and i have multiple components base and addons enabled and tweaked. Recently however i decided to switch to flux (git) based bb deployment following the customer templates (https://repo1.dso.mil/big-bang/customers/template); so i used the gitRepo approach... This however revealed an issue with duplicate id's for a grafana secret. A local template-out revealed indeed a duplicate resource: 1. bigbang/templates/grafana/grafana-env-secret.yaml 2. bigbang/templates/monitoring/grafana-env-secret.yaml When using a git repo as the flux upstream it behaves appearently more strict. ``` Helm install failed for release bigbang/bigbang with chart bigbang@3.22.1: error while running post render on files: may not add resource with an already registered id: Secret.v1.[noGrp]/grafana-env-secret.monitoring ``` I was able to get around this issue by removing the gitlab.redis.password override (revert to default ""). ## BigBang Version ```yaml 3.23.0 ``` I guess solution directions are to: 1. Get rid of one instance 2. Or use the sync secrets resource by Kyverno as used by other components as well.