Open argush3 opened 1 week ago
Hey team! Please add your planning poker estimate with Zenhub @riyazuddinsyed @JazzarKarim @kzdev420 @tshyun24 @chenhongjing @ChrisGabel23
Please add your planning poker estimate with Zenhub @leodube-aot
@riyazuddinsyed just a note that we just deployed this skeleton job to test with the enable-involuntary-dissolutions feature flag off. We'll be pushing this to Prod with the current release.
Here are my test results in Test when I manually ran the job via the OCP CLI.
This ticket is intended to create an intial skeleton scheduled job that will run daily. The job should be minimal and just contain the basic structure of other scheduled jobs.
TODOs
[x] Create skeleton for a scheduled job called “involuntary-dissolutions”. Use email-reminder job as a reference. Note that k8 folder is no longer required
[x] Add minimal required dependencies to requirements related files. Will need to reference legal api model and services classes.
[x] Add/update config.py to contain minimal config. Db config is required for sure.
[x] Create
involuntary_dissolutions.py
which will contain the core logic of the scheduled job.[x] Add/update docker file to be able to run job properly locally.
[x] Add vaults.json and add following value for now. probably just
sentry
,postgres-legal
andlaunchdarkly
underentity
vault will suffice for now.[x] Add/update GH workflows for CI/CD
[x] Verify CI works. Patrick Wei can help if you have issues.
[x] Verify CD works. i.e. job is deployed successfully to dev . Talk to Patrick Wei when you are ready to merge as he may need to do some OCP work to get the job deployed.
[x] Any other work req’d to get job working
[x] Verify job is running on expected schedule. May want to get Patrick to run schedule more frequently initially to verify things are working. Intended schedule is once a day. To test, it is also possible to manually spin up a schedule job in OCP.