aws / aws/sagemaker-distribution
Make Environment Managements works for all conda virtual environments
- Dominant language
- Shell
- Stars
- 154
- Forks
- 120
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 27
Description
### 🚀 The feature, motivation and pitch
Dear Team,
Can we please for the following script add another argument to able to install the packages inside any virtual environment
#!/bin/bash
set -eux
PROJECT_DIR=${SMUS_PROJECT_DIR:-"$HOME/src"}
# Check if the .libs.json file exists
if [ -e $PROJECT_DIR/.libs.json ]; then
lib_config_json=`cat $PROJECT_DIR/.libs.json`
apply_change_to_space=`echo $lib_config_json | jq -r '.ApplyChangeToSpace'`
# Extract conda channels from the config, add `-c ` before each channel and join the strings
conda_channels=`echo $lib_config_json | jq -r '.Python.CondaPackages.Channels | .[]' | sed 's/^/-c /g'`
# Extract conda package spec from the config and join the strings
conda_package=`echo $lib_config_json | jq -r '.Python.CondaPackages.PackageSpecs | .[]'`
if [ ${apply_change_to_space} == "true" -a -n "$conda_package" ]; then
# if conda package spec exists, install the packages
micromamba install --freeze-installed -y $conda_channels $conda_package
fi
fi
### Use case description
_No response_
### Alternatives
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Locate the environment-management shell script containing the shown .libs.json and micromamba install logic, then read how its current environment is selected. Define the argument and verify that the configured packages install into any supported conda virtual environment without changing the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100