Conversation
There was a problem hiding this comment.
Would this be ready on the patch side to run in production? Or should we just add the job to stage for now?
There was a problem hiding this comment.
Hi @rverdile
We could add the job to stage for now. Patch code can take the events, but nothing will happen until:
1] in app-interface , CONTENT_SOURCES_USER is set. I just checked, this is set for both stage and prod.
2] template_advisory_eval=true is in POD_CONFIG. I just checked, this is set to false in a few places in patchman-engine
We should seek @MichaelMraka 's ACK too as he deals with database for patch.
There was a problem hiding this comment.
Let's remove the prod piece of this PR so we can test it in stage first. This job will run as soon as it merges. So I would make sure all the pieces are in place on the Patch side in stage, and then merge this, and verify it ran correctly i.e. the template - advisory relationship is updated in the patch database. You could use gabi to look at the db table.
There was a problem hiding this comment.
OK, dropped the jobs-prod yaml
There was a problem hiding this comment.
I will test with GABI and listener logs in Kibana.
This commit is for stage only. Enables running one-shot send-template-update-events job from HMS-9952 HMS-10772: Add job definition to the deployment template to execute job in HMS-9952
8a4a393 to
7fa98a1
Compare
3 participants
Summary
HMS-10772: Add job to clowdapp deployment template
Enables running one-shot send-template-update-events job from HMS-9952
HMS-10772: Add job definition to the deployment template to execute job in HMS-9952
Testing steps