Hello again, I am looking at building in some redundancy to our pipeline tools and am realizing that much of the data being passed around is dependent on calls to our SG database. It sounds like an obvious enough position, but I am concerned that I will be unable to populate file io windows for asset management in the case that our SG connection goes down for any amount of time.
Are the file path parsing tools made available through SGTK dependent on SG to convert pipeline tokens into valid directory locations? I understand if a window which displays 'all active projects by name' might not be able to refresh, but I can't rely exclusively on internet connectivity for engine level file input/output.
Ideally, I could rely on templates.yml and it's tokenization schema to convert paths and find publish locations without having to derive context from SGTK or concern myself with updating entities.