Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-client/pull/44
I also noted that any update that doesn't change a version is silently
ignored, no error and no effect. desired behaviour is that:
* if the update is a snapshot, simply replace it in the catalog
* if the update is not a snapshot, generate an error
This is NOT to do with this PR; it needs a change in the brooklyn-server
REST API behaviour -- but I only noticed it here. (I was running with
https://github.com/apache/brooklyn-server/pull/645 when observed but I don't
think that is significant.)
The idea is that a workflow where you make a change to a BOM or script,
then `br catalog add` and good things happen if you're on a snapshot version --
do another `br deploy` and you should get the latest version. (And ideally we
could then add an `--update-all-deployments` to `catalog add` and deployments
would be updated!)
Already with this PR it is much easier you just have to remember to bump
the version number but we can do better.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
