Version 3.3.0 - Python Import Inject #9
Merged
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
## Added
- A new expression for injecting values imported from/via Python like so
`${__PY__:alviss.__version__}`
- This uses the `ccptools.tpu.strimp.get_any(...)` to import whatever the
expression key points to and inject into the parsed config
- The use case here is mainly to inject dynamic Python values into Alviss
files "on-demand" like when using [ccp-stencil](https://github.com/ccpgames/ccp-stencil)
templates in a CI/CD pipe so you can have the ever-changing version of the
package you're working on injected automatically into the Alviss config file
used as Context for rendering Docker files, Kube manifests and so on
(similar to how it can be done in `pyproject.toml`)
- This expression also adheres to the normal format of "defaults" (e.g.
`${__PY__:alviss.__version__=Unknown}`) and "required" (e.g.
`${__PY__:alviss.__version__!=}`)
## Added
- A new expression for injecting values imported from/via Python like so
`${__PY__:alviss.__version__}`
- This uses the `ccptools.tpu.strimp.get_any(...)` to import whatever the
expression key points to and inject into the parsed config
- The use case here is mainly to inject dynamic Python values into Alviss
files "on-demand" like when using [ccp-stencil](https://github.com/ccpgames/ccp-stencil)
templates in a CI/CD pipe so you can have the ever-changing version of the
package you're working on injected automatically into the Alviss config file
used as Context for rendering Docker files, Kube manifests and so on
(similar to how it can be done in `pyproject.toml`)
- This expression also adheres to the normal format of "defaults" (e.g.
`${__PY__:alviss.__version__=Unknown}`) and "required" (e.g.
`${__PY__:alviss.__version__!=}`)
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.
[3.3.0] - 2024-05-30
Added
${__PY__:alviss.__version__}ccptools.tpu.strimp.get_any(...)to import whatever theexpression key points to and inject into the parsed config
files "on-demand" like when using ccp-stencil
templates in a CI/CD pipe so you can have the ever-changing version of the
package you're working on injected automatically into the Alviss config file
used as Context for rendering Docker files, Kube manifests and so on
(similar to how it can be done in
pyproject.toml)${__PY__:alviss.__version__=Unknown}) and "required" (e.g.${__PY__:alviss.__version__!=})