mamba-org/provision-with-micromamba

provision a CI instance using micromamba

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stalelast commit May 22, 2023
License: BSD
Runtime: Deprecated runtime

Pinned Snippet

workflow.ymlSHA-pinned

uses: mamba-org/provision-with-micromamba@3c96c0c27676490c63c18bc81f5c51895ac3e0e6 # v16

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
environment-file	Required. Path to the `environment.yml` or `.lock` file for the Conda environment OR `false`. If `false`, only extra-specs will be considered and you should provide channels. If both environment-file and extra-specs are empty, no environment will be created (only `micromamba` will be installed). See the [Conda documentation](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#creating-an-environment-from-an-environment-yml-file) for more information.	yes	environment.yml
environment-name	The name of the Conda environment. Defaults to name from the `environment.yml` file set with environment-file. Required if environment-file is a `.lock` file or `false`, [unless](https://github.com/mamba-org/provision-with-micromamba/issues/54) both environment-file and extra-specs are empty.	—	—
micromamba-version	Version of micromamba to use, eg. `"0.20"`. See <https://github.com/mamba-org/mamba/releases/> for a list of releases.	yes	latest
extra-specs	Additional specifications (packages) to install. Pretty useful when using matrix builds to pin versions of a test/run dependency. For multiple packages, use multiline syntax: ```yaml extra-specs: \| python=3.10 xtensor ``` Note that selectors (e.g. `sel(linux): my-linux-package`, `sel(osx): my-osx-package`, `sel(win): my-win-package`) are available.	—	—
channels	Comma separated list of channels to use in order of priority (eg., `conda-forge,my-private-channel`)	—	—
condarc-file	Path to a `.condarc` file to use. See the [Conda documentation](https://docs.conda.io/projects/conda/en/latest/user-guide/configuration/) for more information.	—	—
channel-priority	Channel priority to use. One of `"strict"`, `"flexible"`, and `"disabled"`. See https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-channels.html#strict-channel-priority for more information.	yes	strict
cache-downloads	If `true`, cache downloaded packages across calls to the provision-with-micromamba action. Cache invalidation can be controlled using the cache-downloads-key option.	yes	false
cache-downloads-key	Custom download cache key used with `cache-downloads: true`. The default download cache key will invalidate the cache once per day.	—	—
cache-env	If `true`, cache installed environments across calls to the provision-with-micromamba action. Cache invalidation can be controlled using the cache-env-key option.	yes	false
cache-env-key	Custom environment cache key used with `cache-env: true`. With the default environment cache key, separate caches will be created for each operating system (eg., Linux) and platform (eg., x64) and day (eg., 2022-01-31), and the cache will be invalidated whenever the contents of environment-file or extra-specs change.	—	—
log-level	Micromamba log level to use. One of `"trace"`, `"debug"`, `"info"`, `"warning"`, `"error"`, `"critical"`, `"off"`.	—	warning
installer-url	Base URL to fetch Micromamba from. Files will be downloaded from `<base url>/<platform>/<version>`, eg. <https://micro.mamba.pm/api/micromamba/linux-64/latest>.	yes	https://micro.mamba.pm/api/micromamba
condarc-options	More options to append to `.condarc`. Must be a string of valid YAML: ```yaml condarc-options: \| proxy_servers: http: ... ```	—	—
post-deinit	Attempt to undo any modifications done to `.bashrc` etc. in the post action of the workflow. This is useful for self-hosted runners that keep the state of the system. One of `"auto"`, `"true"` or `"false"`. If set to `"auto"`, behaves like `"true"` if the micromamba version used supports `micromamba shell deinit` (i.e. `micromamba>=0.25.0`).	yes	auto

Outputs

no outputs