Plugin vs Tool Versioning Strategy #206
Replies: 5 comments 6 replies
-
Only implication for not deciding this now is if there's a conflict with our version convention for plugins and a released tool version. |
Beta Was this translation helpful? Give feedback.
-
Per #307 the official BitOps images will be 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. The version parameter could be provided via config like: bitops:
plugins:
terraform:
source: https://github.com/bitops-plugins/terraform
version: 1.2.3 # <-- new setting and so Here tool version = plugin version, where version is just a parameter and not a repo git tag. |
Beta Was this translation helpful? Give feedback.
-
Thanks @armab ! I commented on the dynamic install ticket #316 . Additionally, I agree with what you said that our warnings should clearly state that this is for testing/development purposes only and should NOT be used for a production environment and encourage users to pre-package their custom image. |
Beta Was this translation helpful? Give feedback.
-
with #315 and #316, I think we can lock this conversation. Thoughts? |
Beta Was this translation helpful? Give feedback.
-
@armab can we also get tickets for the following? Additional Effort in any case (i.e. new tickets)The following are in addition to the "Additional effort for this option" for the selected option
|
Beta Was this translation helpful? Give feedback.
-
How should we handle the plugin repo versions compared to the plugin's tool version.
Terraform for example might have
0.12.*
Options
1.0.0-tf0.12.0
Beta Was this translation helpful? Give feedback.
All reactions