You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement flag for CA to shut off in case of fails - probably a new config setting rather than changing the normal schedule. Check 'are we off' before sending
Tasks
Definitely in scope for this card:
create a new storage container for config in tf
create a new storage container for config for running locally
create config files for all envs with CADPH and on/off flag
prod
staging
PR? PR envs won't each have their own config files - should they look to local, have defaults in parsing, something else?
internal
dev
local
also need to add a step in docker-compose to copy over this file
config retrieval client in web app
config parsing utility in web app
use queue messages in retrieval step to look up config
in retrieval step, use config to determine whether to call external SFTP site
ADR and README updates
configs in Azure
config keys as org names in RS (vs sender/receiver)
filepath naming convention?
Maybe in scope for this card:
in retrieval step, use config to build file paths
new file paths will be like /sftp/ca-phl/import
this is when we’d check if a connection was turned off
use file paths to look up config in import/RS step
DevEx/OpEx
Implement flag for CA to shut off in case of fails - probably a new config setting rather than changing the normal schedule. Check 'are we off' before sending
Tasks
Definitely in scope for this card:
local
, have defaults in parsing, something else?Maybe in scope for this card:
/sftp/ca-phl/import
/sftp/ca-phl/import
Additional Context
See notes here: https://www.notion.so/flexion-cdc-ti/Brainstorming-for-config-spike-1425955365f58011a8e1e7419fd4ce87?pvs=4#1435955365f5801ea83dd2a0c508aa91
The text was updated successfully, but these errors were encountered: