Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Been relying on this pretty extensively and it is SUPER cool. It's not finished but I've been modifying the structure so there is a third kind of node. I'm just calling it a broker for now but essentially I wanted to test nodes that could produce and consume. The only way I could get it to work properly was to have the broker nodes
depends_on
on the nfd nodes then register faces/routes to them. I run nfd-autoreg on the nfd nodes with some base prefix I had to make sure matched what was in the consumer and produce env... as opposed to the original routing structure where the faces/route registration pattern follows the docker-compose dependency hierarchy and creates a unidirectional interest path from consumer to producer. Anyway, neither here nor there, just wanted to add some flavor to a very banal PR.