Skip to content

Add option to save context to environment instead of a file #211

@Nadegamra

Description

@Nadegamra

Currently itp context commands always save iTwin and iModel IDs to a file in the cache directory. This could cause issues, for example.: when running multiple automated workflows. I see a few possible solutions for this issue:

  1. Make context commands behave differently depending on token type:
    • When interactive login is used: context is saved to a file in cache directory
    • When service login is used: context is saved to current environment.
  2. Have a command flag, that gives the user an option to use context commands to save to environment instead of a file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Enhancement.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions