You've already forked helm-actions

To be discussed. In https://gitea.com/gitea/helm-actions/issues/9#issuecomment-1002191 and https://gitea.com/gitea/helm-actions/pulls/13 I described that a migration of provisioning is currently not feasible due to - helm limitations - You are forced to repeat a lot of stuff for the default branch - helm-actions cannot read values of the helm-gitea chart to fix this - No agreement about making helm-gitea a optional dependency of helm-actions can be reached at the moment # Proposal - Create a new repository that includes both helm-gitea **and** helm-actions - Provisioning leaves this repository as well like it did in helm-gitea - Create that as gitea/helm-stack or whatever name - Provisioning code and tests moves to gitea/helm-stack We would need help with the repository creation Reviewed-on: https://gitea.com/gitea/helm-actions/pulls/15 Reviewed-by: DaanSelen <daanselen@noreply.gitea.com> Co-authored-by: ChristopherHX <christopherhx@noreply.gitea.com> Co-committed-by: ChristopherHX <christopherhx@noreply.gitea.com>
10 lines
346 B
YAML
10 lines
346 B
YAML
{{- if .Values.enabled -}}
|
|
|
|
{{- if or (empty .Values.existingSecret) (empty .Values.existingSecretKey) -}}
|
|
{{- fail "existingSecret and existingSecretKey are required when provisioning is disabled" -}}
|
|
{{- end -}}
|
|
{{- if not .Values.giteaRootURL -}}
|
|
{{- fail "giteaRootURL is required" -}}
|
|
{{- end -}}
|
|
{{- end -}}
|