You've already forked helm-actions
8c95dcd282
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>
36 lines
1.2 KiB
YAML
36 lines
1.2 KiB
YAML
suite: actions template | consistency checks
|
|
release:
|
|
name: gitea-unittests
|
|
namespace: testing
|
|
templates:
|
|
- templates/01-consistency-checks.yaml
|
|
tests:
|
|
- it: fails when provisioning is disabled BUT existingSecret and existingSecretKey are missing
|
|
set:
|
|
enabled: true
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "existingSecret and existingSecretKey are required when provisioning is disabled"
|
|
- it: fails when provisioning is disabled BUT existingSecretKey is missing
|
|
set:
|
|
enabled: true
|
|
existingSecret: "my-secret"
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "existingSecret and existingSecretKey are required when provisioning is disabled"
|
|
- it: fails when provisioning is disabled BUT existingSecret is missing
|
|
set:
|
|
enabled: true
|
|
existingSecretKey: "my-secret-key"
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "existingSecret and existingSecretKey are required when provisioning is disabled"
|
|
- it: fails when LOCAL_ROOT_URL is missing
|
|
set:
|
|
enabled: true
|
|
existingSecret: "my-secret"
|
|
existingSecretKey: "my-secret-key"
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "giteaRootURL is required"
|