{Integration Name}¶
Introduction¶
UPDATE ME
This section should include a brief description of the integration and why it exists. For more information on creating valuable documentation, review the.
UPDATE ME
Development Notes¶
UPDATE ME
This section should include any notes a developer should know about the integration which is not immediately apparent from the introduction or from the code itself. This may include (but is not limited to) notes regarding special setup for testing, additional documentation, or integration structure.
UPDATE ME
Config Maps and Secrets¶
UPDATE ME
This section should include a list of config maps and secrets relevant to the integration.
UPDATE ME
¶
Sequence Diagram¶
sequenceDiagram
participant adirondack as data-01.datacenter.adirondacksolutions.com
participant edw as EDW
participant k8s as Kubernetes
participant OD as OneDrive
participant ohio as oit-mft-lp002.oit.ohio.edu
adirondack ->> k8s: OHIO_ROOMPACT_EXPORT.csv
k8s ->> k8s: change column names
edw ->> k8s: download photos from EREZLIFE_STUDENT_V
k8s ->> ohio: OHIO_ROOMPACT_EXPORT.csv
k8s ->> ohio: Photos: {PID}.jpg
k8s ->> OD: OHIO_ROOMPACT_EXPORT.csv
Patch Testing Instructions¶
New Workflow with specified versions
file name change TEST
deploy-mkdocs.yaml name change TEST
delete gh pages branch TEST