-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cli for use in NPM scripts #168
Open
thewtex
wants to merge
9
commits into
mamba-org:main
Choose a base branch
from
thewtex:cli
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When used in NPM scripts, `setup-micromamba` provides a convenient way to download micromamba and create conda environments. Set options through environment variables in invocation. If micromamba has already been downloaded or an environment already exists, it will not be recreated. Example: ``` "scripts": { [...] "micromamba": "MICROMAMBA_ROOT_PATH=micromamba CREATE_ENVIRONMENT=true CREATE_ARGS=\"python=3.11\" ENVIRONMENT_NAME=test-env setup-micromamba", [...] ``` We re-use the mocking core. Determination of the core backend is moved to a separate module to prevent duplication and circular imports. The default micromamba bin path is set to `${MICROMAMBA_ROOT_PATH}/micromamba` if `MICROMAMBA_ROOT_PATH` is set. Have the mocking core respect the log level.
And running passing argument other that a shell script.
Example: setup-micromamba --micromamba-root-path micromamba debug --init-shell none --create-environment true --environment-file environment.yml --generate-run-shell true --micromamba-run-shell-path ./micromamba/run-shell --log-level debug
Separate run() invocations in src/main.ts and src/operations.ts.
Avoid run side effects.
In an NPM run script. Todo: verify that this is not set in GitHub Actions.
Results in an error in GitHub Actions: ``` Error: Unable to process command ' ::add-path::<the path> Error: The `add-path` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When used in NPM scripts,
setup-micromamba
provides a convenient way to download micromamba and create conda environments.Set options through environment variables or command line flags in invocation. Command line flag parsing is very basic. If micromamba has already been downloaded or an environment already exists, it will not be recreated.
Example:
or
We re-use the mocking core. Determination of the core backend is moved to a separate module to prevent duplication and circular imports.
The default micro mamba bin path is set to
${MICROMAMBA_ROOT_PATH}/micromamba
ifMICROMAMBA_ROOT_PATH
is set.Have the mocking core respect the log level.