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
As a support engineer I would like to be able to query blueapi for the state of the scratch directory to aid in installation/debugging, in particular I would like to know:
Which packages are installed via the scratch directory
Which of those replaced packages that were already in the environment
The versions checked out
Whether uncommitted changes are present
Acceptance Criteria
There are REST endpoint(s) for querying all of the above
They are tested
They are supported by the CLI
The text was updated successfully, but these errors were encountered:
In order to set up the scratch area you have to run blueapi -c <config> setup-scratch and then run blueapi -c <config> serve. This means that blueapi serve "forgets" where the scratch area is and what it installed from it, that information lives and dies with the setup-scratch process. This is a little annoying for us, but it may be an opportunity to deal with #646 at the same time. If you can think of a way to reunify the two configs.
As a support engineer I would like to be able to query blueapi for the state of the scratch directory to aid in installation/debugging, in particular I would like to know:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: