@edsiper @stevehipwell @naseemkullah please review it.

@captainpro-eng wont this implementation churn the uid with each Helm operation?

wont this implementation churn the uid with each Helm operation?

didn't get your point. please explain it.

@captainpro-eng the randAlphaNum function would cause the uid to change each time you ran helm upgrade.

To achieve what you're looking at doing I'd suggest using the following function which would be deterministic (assuming the result is a valid type for uid).

{{/*
Create the uid for grafana fluent-bit dashboard
*/}}
{{- define "fluent-bit.dashboard.uid" -}}
{{- sha256sum (printf "%s/%s" .Release.Namespace .Release.Name) }}
{{- end }}

@captainpro-eng the randAlphaNum function would cause the uid to change each time you ran helm upgrade.

To achieve what you're looking at doing I'd suggest using the following function which would be deterministic (assuming the result is a valid type for uid).

{{/*
Create the uid for grafana fluent-bit dashboard
*/}}
{{- define "fluent-bit.dashboard.uid" -}}
{{- sha256sum (printf "%s/%s" .Release.Namespace .Release.Name) }}
{{- end }}

got it 👍

@captainpro-eng you will need to update the Chart.yaml to bump the version and change the release note annotations. Could you also squash your commits if possible.

@stevehipwell changes has been added.

@captainpro-eng could you fix the failing DCO?

@captainpro-eng could you fix the failing DCO?

please review it.

@captainpro-eng I've just checked the docs and it looks like this behaviour could be achieved by just setting the value to null.

okay let me check

@captainpro-eng I've just checked the docs and it looks like this behaviour could be achieved by just setting the value to null.

i tested with null values facing same issue "the same UID is used more than once". if we set null it is genrating same uid for all helm release.

i tested with null values facing same issue "the same UID is used more than once". if we set null it is genrating same uid for all helm release.

@captainpro-eng did you also set the id to null?

i tested with null values facing same issue "the same UID is used more than once". if we set null it is genrating same uid for all helm release.

@captainpro-eng did you also set the id to null?

id is already null.