[DRAFT] Introduce session concept for variables

[0hsn]

What

When we run a spec it should run under a run session (similar concept to run id for validation asserts). Session ensure all input and exposed data is stored and transferable in closed encrypted way.

Why

CHKware needs

• a reliable system to transfer data in-between command invocation
• a system where sessions are uniquely identifiable, and addressable from external systems
• sessions are stored to be referenced later
• SESSIONS are for external system to pass values to other system, this can not be addressed locally (fetch, validate)

How

• Enable session from command line with -S=? or --session=?

  • This is a hidden option
  • Accept a session name eg: someRandomSession
  • Saves a file in session path <CHK_SESSION_PATH>/someRandomSession.json

  [Need thinking]

  • Do not check if given session name already exists, always overwrite. This is user's choice to make it random.
    • What happens to session name is used in validate but not in fetch, system will not be able to find expected data?

• Use ./.chkware_cache as chk ... caching directory.

• Create session directory in cache directory named ./.chkware_cache/sessions.

  • <CHK_SESSION_PATH> can be used to override the directory