PACKAGE_ENV_VARS for package environment variable mapping #84
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
tiff-ritz
changed the title
tiff-ritz
force-pushed
the
main
branch
2 times, most recently
from
b95a6ce to
2e9918a
Compare
tiff-ritz
changed the title
# This is the 1st commit message: added code to set GIT_EXEC_PATH while installing packages. Added a FromStr implementation to debian::MultiarchName in order to implement a unit test document adding GIT_EXEC_PATH in the readme table of environment variables # This is the commit message #2: add setting of GS_LIB
Added a FromStr implementation to debian::MultiarchName Implment functionality to load the environment variables associate with packages from the project.toml file use PACKAGE_ENV_VARS constand to map default env vars to be defined if the package is in the project.toml file - these can be overwritten by the values in the project.toml file define the package_env_vars before the env vars in the project.toml file update README to reflect the PACKAGE_ENV_VARS testing the buildpack, added a variable for skipped_packages. Will incorporate that into install_packages move the env logic into configure_layer_environment. Iterate through the skipped_packages to make sure all the env vars are set and the post install command are run flushed out a test in order to accomindate the new parameters passed to configure_layer_environment finished the test for skipped packages update the unit test to use a fixture to create the env correctly use a fixture for the test project.toml file; update the README
remove configurable env and post commands,
tiff-ritz
changed the title
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.
The buildpack includes a set of default environment variables for each package, known as
PACKAGE_ENV_VARS. These default environment variables are applied during the build process. However, you can override these default values by specifying environment variables in the project.toml file.If a package is listed in the project.toml file with environment variables under the env key, those variables will take precedence over the default
PACKAGE_ENV_VARS.Added unit tests to:
Integration Tests added: