This ticket is intended to create an initial skeleton scheduled job that will run daily. The job should be minimal and just contain the basic structure of other scheduled jobs. The PR for the involuntary dissolutions job will be a good reference as the skeleton should be fairly similar.
TODOs
[x] Create skeleton for a scheduled job called “involuntary-dissolutions”. Use PR for the involuntary dissolutions 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 furnish.py which will contain the core logic of the scheduled job.
[x] setup sentry related code
[x] setup launchdarkly related code
[x] add logic to only run code when enable-involuntary-dissolution FF is on
[x] setup job such that unit tests can run
[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 and launchdarkly under entity vault will suffice for now.
[x] Add/update GH workflows for CI/CD
[x] CI workflow
[x] CD workflow
[x] Verify CI works. Patrick Wei can help if you have issues.
[x] Verify CD works. i.e. job is deployed successfully to dev . Note that there will be some work that needs to be done in OCP to get things working. Talk to Argus or Hongjing to figure out what was req'd to get involuntary dissolutions job running in OCP.
[x] Any other work req’d to get job working
[x] Verify job is running on expected schedule. May want 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.
This ticket is intended to create an initial skeleton scheduled job that will run daily. The job should be minimal and just contain the basic structure of other scheduled jobs. The PR for the involuntary dissolutions job will be a good reference as the skeleton should be fairly similar.
TODOs
furnish.py
which will contain the core logic of the scheduled job.sentry
,postgres-legal
andlaunchdarkly
underentity
vault will suffice for now.