Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support application-version-set hook tool
See original GitHub issueI can’t find an interface to the application-version-set hook tool. Has it been deprecated, or is it just missing from the framework?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Hook tool - Juju
application-version-set allows you to specify which version of the application is deployed. This will be provided to users via juju status . From...
Read more >Command 'juju help-tool' - doc - Charmhub
Usage: juju help-tool [tool] Summary: Show help on a Juju charm hook tool. ... add metrics application-version-set specify which version of the application ......
Read more >button hook - Amazon.com
Vive Button Hook - Zipper Pull Helper - Dressing Aid Assist Device Tool for Arthritis, Dexterity Handle Grip. 1 Count (Pack of 1)....
Read more >Can't set application version string in K8s charm
I checked the implementation and for k8s charms, the application version is supposed to show the docker image path. However, there's a bug ......
Read more >Hook Tools - Equalizer®
Picture for category Hook Tools ... 3 products found. Picture of MT1295 • Narrow Nose Hook Tool ... $12.00. Picture of Double Bend...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It needs agreement between the framework and juju itself. We can’t call it one thing here and a different thing there. Also, if this field is in the application, and it’s called version, it’s indeed the application version not the workload version. Each unit will have its own workload, potentially with different versions.
Ultimately this is a poor man’s way to communicate structured information to the user. Eventually we need a proper way to communicate arbitrary structured data.
@jameinel Makes sense, and that makes it even worse. It’s inconsistent inside juju itself already.