Skip to content

Commit bfc998a

Browse files
authored
Merge pull request #581 from ChandanSharma61370/Issue_553_Documentation_update_policy_register
Issue #533 - Policy register documentation fix, adding business polic…
2 parents 954d86b + f377b02 commit bfc998a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

edge/evtstreams/cpu2evtstreams/PolicyRegister.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ hzn exchange service listpolicy IBM/ibm.cpu2evtstreams_1.4.3_amd64
8282

8383
### Deployment Policy
8484

85-
- 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.
85+
- 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.
8686

8787
- 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).
8888

0 commit comments

Comments
 (0)