luceda-cornerstone/provision-with-micromamba
provision a CI instance using micromamba
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| environment-file | The environment.yml or .lock file for the conda environment. If 'false', no enviroment will be created (only Micromamba will be installed) and you should provide 'channels'. | yes | environment.yml |
| environment-name | The name of the conda environment (defaults to name from the environment.yml file). Required if 'environment-file' is a '.lock' file or 'false'. | no | — |
| micromamba-version | Version of micromamba to use, eg. '0.20' (default 'latest'). | no | 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 (see examples). Note that selectors (e.g. `sel(linux): my-linux-package`, `sel(osx): my-osx-package`, `sel(win): my-win-package`) are available. | no | "" |
| channels | Comma separated list of channels to use in order of priority (eg., `conda-forge,my-private-channel`) | no | "" |
| 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. | — | 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. | no | — |
| 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. | — | 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. | no | — |
Outputs
no outputs