-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"serviceVersionRange" in Hello World deployment.policy.json example is incorrect #492
Comments
@t-fine This PR has been open for a while. It fixes a typo in a json file. Would be great if you could review / merge it. |
Hey @johnwalicki sorry for the delay here ... completely slipped my mind after the examples working group meeting, then out last week for thanksgiving ... looking into this now! |
@johnwalicki as far as I can tell when digging into this, there should be no issue including the string
in addition to many exchange return messages on this page... https://github.ibm.com/Edge-Fabric/exchange-api/blob/11cca8b2f6c12628558ad0ea7bec6827acb0931e/doc/openapi-3.json#L1137 |
@johnwalicki can you remind me, when you were attempting this initially, did it publish to the exchange with |
@t-fine @johnwalicki The correct syntax is
|
Interesting. I use semantic version syntax in several of my projects. I've never heard of "[)" I still like pinning a deployment policy to a specific |
Sounds good! Closing. |
Late comment, but I think it would be good to note somewhere that we're using semantic version syntax in that way, since the "[)" looked odd to me as well. |
The
https://github.com/open-horizon/examples/blob/master/edge/services/helloworld/policy/deployment.policy.json#L25
file includes an example of a deployment.policy.json with a userInput environment variable definition. It shows a
serviceVersionRange
key / value pair that is incorrect json. The closing)
should be a]
"serviceVersionRange": "[0.0.0,INFINITY)",
While it is interesting to show in the example that the serviceVersionRange array can list many versions, to make it relevant to the example, it would be better to specify.
"serviceVersionRange": "[$SERVICE_VERSION]",
or
"serviceVersionRange": "[$SERVICE_VERSION,INFINITY]",
The text was updated successfully, but these errors were encountered: