We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At present, it is possible to define 2 cronjobs in .lagoon.yml with the same name.
.lagoon.yml
- name: test-cronjobs schedule: "M * * * *" command: /app/console do:stuff service: cli - name: test-cronjobs schedule: "M * * * *" command: /app/console do:something:different service: cli
Only the last one will 'win', and only a single cronjob will be made. This is confusing for the end user.
Either pass the build with warnings, or fail the build entirely. Either way, we should inform the use that they need to adjust their .lagoon.yml file.
The text was updated successfully, but these errors were encountered:
I think failure would be better, as long as the failure can happen early
Sorry, something went wrong.
No branches or pull requests
At present, it is possible to define 2 cronjobs in
.lagoon.yml
with the same name.Only the last one will 'win', and only a single cronjob will be made. This is confusing for the end user.
Proposed solution
Either pass the build with warnings, or fail the build entirely. Either way, we should inform the use that they need to adjust their
.lagoon.yml
file.The text was updated successfully, but these errors were encountered: