Skip to content

add fields to configure plugin conda executable and env paths#2654

Open
emlys wants to merge 13 commits into
natcap:mainfrom
emlys:feature/2645
Open

add fields to configure plugin conda executable and env paths#2654
emlys wants to merge 13 commits into
natcap:mainfrom
emlys:feature/2645

Conversation

@emlys

@emlys emlys commented Jul 8, 2026

Copy link
Copy Markdown
Member

Description

Fixes #2645, fixes #2646
Add an interface in the "Manage Plugins" modal to change the configured conda executable and plugin environment paths (equivalent to the micromamba and plugins.<plugin ID>.env properties in config.json).

I added defaultMicromamba and plugins.<plugin ID>.defaultEnv properties to the config.json to track the original values so that they can be reset if needed.

Needed to mock the plugin data returned from GET_SETTING in a couple more tests.

Checklist

  • Updated HISTORY.rst and link to any relevant issue (if these changes are user-facing)
  • Updated the user's guide (if needed)
  • Tested the Workbench UI (if relevant)

fs.writeFileSync(baseEnvYMLPath, baseEnvYMLContents);
await spawnWithLogging(micromamba, [
'create', '--yes', '--prefix', `"${baseEnvPrefix}"`,
'env', 'create', '--yes', '--prefix', `"${baseEnvPrefix}"`,

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that "env create" rather than just "create" is necessary for compatibility with conda.

@emlys emlys requested a review from emilyanndavis July 15, 2026 19:54
@emlys emlys marked this pull request as ready for review July 15, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workbench option to set a user-defined conda env for a plugin Workbench option to use a user-provided conda installation

1 participant