You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A message from Glen...
"It is unfortunate that the examples in the open-horizon/examples repo inconsistently use the horizon subdirectory and the policy subdirectory. I had forgotten how bad this was but today I am trying to write up something about how to use pattern and policy and I wanted to point at the examples repo but then rediscovered the inconsistency there."
The original reason for having two sets of policy files in the horizon and policy directories was to have one that the exchangePublish.sh script uses when populating a new exchange (the horizon dir), and one set for users to leverage when walking through the "Creating your own ..." README flow so there wouldn't be two agreements that deploy the helloworld service possible causing confusion as well.
The text was updated successfully, but these errors were encountered:
@saurav1004 Take a look at our newer example services for a good pattern or example to follow regarding files living in a single folder rather than "horizon" or "policy" directories:
@saurav1004 in regards to the files in policy/ ... perhaps their creation could be worked into the steps of the "Creating Your Own Hello World Edge Service" so there is no actual file to save ... just thinking
A message from Glen...
"It is unfortunate that the examples in the open-horizon/examples repo inconsistently use the
horizon
subdirectory and thepolicy
subdirectory. I had forgotten how bad this was but today I am trying to write up something about how to use pattern and policy and I wanted to point at the examples repo but then rediscovered the inconsistency there."The original reason for having two sets of policy files in the
horizon
andpolicy
directories was to have one that theexchangePublish.sh
script uses when populating a new exchange (thehorizon
dir), and one set for users to leverage when walking through the "Creating your own ..." README flow so there wouldn't be two agreements that deploy the helloworld service possible causing confusion as well.The text was updated successfully, but these errors were encountered: