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
While our current method of templating yamls to generate very large jedi.yamls is simple and effective, we still would like to migrate to using JCB. For a couple of reasons:
JCB is more powerful in configuring the jedi yamls especially with the observation_chronicle function.
GDASApp already uses JCB and we should unify methods and tools between systems as much as possible. This also means that global and regional teams can work together more effectively vs having two completely different systems.
Description
While our current method of templating yamls to generate very large jedi.yamls is simple and effective, we still would like to migrate to using JCB. For a couple of reasons:
Requirements
Acceptance Criteria (Definition of Done)
Dependencies
None
The text was updated successfully, but these errors were encountered: