Skip to content

Commit

Permalink
Merge pull request #581 from ChandanSharma61370/Issue_553_Documentati…
Browse files Browse the repository at this point in the history
…on_update_policy_register

Issue #533 - Policy register documentation fix, adding business polic…
  • Loading branch information
johnwalicki authored Mar 1, 2023
2 parents 954d86b + f377b02 commit bfc998a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion edge/evtstreams/cpu2evtstreams/PolicyRegister.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ hzn exchange service listpolicy IBM/ibm.cpu2evtstreams_1.4.3_amd64

### Deployment Policy

- Deployment Policy (sometimes called Deployment Policy) is what ties together Edge Nodes, Published Services, and the Policies defined for each of those, making it roughly analogous to the Deployment Patterns you have previously worked with.
- Deployment Policy (sometimes called Business Policy) is what ties together Edge Nodes, Published Services, and the Policies defined for each of those, making it roughly analogous to the Deployment Patterns you have previously worked with.

- Deployment Policy, like the other two Policy types, contains a set of `properties` and a set of `constraints`, but it contains other things as well. For example, it explicitly identifies the Service it will cause to be deployed onto Edge Nodes if negotiation is successful, in addition to configuration variable values, performing the equivalent function to the `-f horizon/userinput.json` clause of a Deployment Pattern `hzn register ...` command. The Deployment Policy approach for configuration values is more powerful because this operation can be performed centrally (no need to connect directly to the Edge Node).

Expand Down

0 comments on commit bfc998a

Please sign in to comment.