You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here tool version = plugin version, where version is just a parameter and not a repo git tag.
That would fit customized use cases and environments which is the main purpose of building the custom bitops image with the chosen plugins.
Started with the #307, it's just a matter of time when this will pop-up more.
Per #307 the official BitOps images are now packaging and providing the latest tools by default.
However, user should be able to pin the tool version (ansible==1.2.3, terraform=3.4.5). This might be achievable when building their custom BitOps Docker image https://bitovi.github.io/bitops/plugins/#creating-your-own-bitops-image
The version parameter could be provided via config like:
and so
1.2.3
will be passed to the plugininstall.sh
to install the needed tool version:https://github.com/bitops-plugins/terraform/blob/b189c2dd7cb38e7e883837f0f3204e5b7e8a6e6b/install.sh#L13-L14
Here tool version = plugin version, where version is just a parameter and not a repo git tag.
That would fit customized use cases and environments which is the main purpose of building the custom bitops image with the chosen plugins.
Started with the #307, it's just a matter of time when this will pop-up more.
Previous Discussions
The text was updated successfully, but these errors were encountered: