Skip to content

a365 CLI does not respect local configration when trying to create multiple blueprints #162

@MattB-msft

Description

@MattB-msft

Once A365 CLI creates a blueprint, its storing a config file in %LOCALAPPDATA%\Microsoft.Agents.A365.DevTools.Cli.
if I change my local config, or create a separate config in another directory via copy and modify, it ignores my local settings and config file and attempts to use the one in the %LOCALAPPDATA%\Microsoft.Agents.A365.DevTools.Cli directory.

In order to create a 2 blueprints on the same machine and be able to work with them, I must delete the content of the %LOCALAPPDATA%\Microsoft.Agents.A365.DevTools.Cli each time I switch contexts.

Would recommend using %LOCALAPPDATA%\Microsoft.Agents.A365.DevTools.Cli only for token cache \ logs and remove all other configuration writing from there to allow the developer to manage configurations in the file system directly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions