GIT Connection for JS7 Configurations

Introduction

JS7 JOC should be able to connect to GIT repositories to store JS7 configuration objects. Configuration objects can be versionized (tagged) and rolled out to different JS7 instances via GIT.

Use Cases

GIT Use Cases
1. Single User (Backup tool)
- Use Case
user versions specific states of a JS7 object configuration

1. simple structure

- Use case
- simple versioning repository
- DB is the leading system (???)
- Repository used for user versioning only
- Single branch
- Version can overwrite local (DB) versions as new configurations
- new local configurstion share version from repository (next version +1 or next version Snapshot)

- git structure needed
- single branch
-

- git commands needed
- add
- delete
- commit
- pull
- push
- tag

2. dev, test, prod

- Use case
- Different versioning for different branches (dev, test, prod)
- DB is the leading system (???) (single DB? for each branch?)
- Repository used for user versioning only
- merges from branch to branch possible?
- Version can overwrite local (DB) versions as new configurations
- new local configuration share latest version from DB (next version +1 or next version Snapshot)


Repository
|
|
/\
/ |\
/ | \
JOC Dev - JOC Test - JOC Prod
DB Dev DB Test DB Prod
JS7 Infra JS7 Infra JS7 Infra