json schema on forge return 404
roock opened this issue ยท 8 comments
The documented urls for bolt are returning a 404 error.
$ curl https://forgeapi.puppet.com/schemas/bolt-defaults.json
{
"message": "404 Not Found",
"errors": [
"The requested resource cannot be found"
]
}
$ curl https://forgeapi.puppet.com/schemas/bolt-inventory.json
{
"message": "404 Not Found",
"errors": [
"The requested resource cannot be found"
]
}
$ curl https://forgeapi.puppet.com/schemas/bolt-yaml-plan.json
{
"message": "404 Not Found",
"errors": [
"The requested resource cannot be found"
]
}
Thanks, i'll check with the forge team about getting those back
Hi @roock, Thanks for reporting the issue, I have reviewed the documented endpoints, and they seems to be broken right now. I will raise the same with team internally.
Till we resolve this issue here are alternative URL which you can start consuming :
Looks like the endpoints got fixed at some point! I'm able to hit them now.
$ curl -s https://forgeapi.puppet.com/schemas/bolt-yaml-plan.json | head
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Bolt YAML Plan",
"description": "Bolt YAML Plan Schema",
"type": "object",
"required": ["steps"],
"additionalProperties": false,
"properties": {
"description": {
"description": "A description of the plan. This description will show in 'bolt plan show' and 'Get-BoltPlan' output.",
I can confirm that I can reach all endpoints, although one of the files is invalid json (wrong comma on line 340).
curl https://forgeapi.puppet.com/schemas/bolt-yaml-plan.json |jq
jq: parse error: Expected another key-value pair at line 341, column 3
It appears like bolt-yaml-plan.json
is the only one that isn't auto-generated. So removing the stray trailing comma should be safe I think.
Yes, it looks like so. I've opened a PR which fixes the json syntax error.
Thanks!
From my side of view the issue can be closed.