Workflows: Fix issue where forks would still run EE tests
Description
This is my last workflow-related PR, and it is a bug fix.
Minor annoyance. I saw workflow failures on my fork on the EE job, which was not supposed to run. It was due to a bug introduced in #426 (closed) where it does not check if the LICENSE_ENCRYPTION_PASSWORD is set, so the workflow would trigger anyway from the fork's main branch.
I copied this workflow code over from the push.yml
one.
In the future we can probably de-duplicate some workflow config, but at the moment there are some bugs with workflow templating.
- https://github.community/t/support-for-yaml-anchors/16128
- https://github.community/t/ref-head-in-reusable-workflows/203690/66
PR Checklist
-
Resource attributes match 1:1 the names and structure of the API resource in the GitLab API documentation. -
Examples are updated with: - A *.tf file for the resource/s with at least one usage example
- A *.sh file for the resource/s with an import example (if applicable)
-
New resources have at minimum a basic test with three steps: - Create the resource
- Update the attributes
- Import the resource
-
No new //lintignore
comments that came from copied code. Linter rules are meant to be enforced on new code.