Github user mikezaccardo commented on the issue:
https://github.com/apache/brooklyn-server/pull/546
@grkvlt this would indeed be useful for the Hyperledger Fabric
multi-cluster in place of this entity:
Github user grkvlt commented on the issue:
https://github.com/apache/brooklyn-server/pull/546
@mikezaccardo is this still useful, e.g. for HLF blueprints?
---
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
Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/546
I feel like this will soon be superseded, by being able to point at some
shared-scoped atomic integer and request a `getAndIncrement` directly in YAML
as part of `start`. Haven't looked
Github user grkvlt commented on the issue:
https://github.com/apache/brooklyn-server/pull/546
@aledsage the use case in mind was to sequentially number across multiple
clusters (i.e a fabric spread around several locations)
---
If your project is set up for it, you can reply to this
