Add new param and option to trigger cronjob (BACK-708) #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dakad
force-pushed
the
task/BACK-708_trigger_cronjob
branch
from
b63d0e4 to
74411a0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Associated ticket number and/or AirBrake error?
BACK-708
Due Date or Desirable Merge
By the end of the QAWAII Sprint (11/11)
How has this been tested?
Locally, by building and using the on the apptweak-staging https://ci.apptweak.com/teams/apptweak/pipelines/apptweak-staging/jobs/rails-migration/builds/26
Anticipated impact
Allow Concourse to use
puttask to trigger a CronJob on KuberbenetesHow do you plan to monitor the change in prod to make sure it's working?
/
Checklist
[ ] My change includes a database modification