DevOps Community Sponsored by Cloud Posse

SweetOps

```11:10:02     Error
11:10:02
11:10:02     **Error:** Atmos manifest JSON Schema validation error in the file
11:10:02     'azure/eastus/prd/app-47.yaml': { "valid": false,
11:10:02     "errors": [ { "keywordLocation": "", "absoluteKeywordLocation":
11:10:02     "<https://json.schemastore.org/atmos-manifest.json#>", "instanceLocation": "",
11:10:02     "error": "doesn't validate with <https://json.schemastore.org/atmos->
11:10:02     manifest.json#" }, { "keywordLocation": "/type", "absoluteKeywordLocation":
11:10:02     "<https://json.schemastore.org/atmos-manifest.json#/type>", "instanceLocation":
11:10:02     "", "error": "expected object, but got null" } ] }```
This appears to happen while running `atmos describe stacks --process-templates=false` when we have a json schema configured for any stack and atmos encounters a stack yaml that is fully commented out

I suspect we can probably add something to the json schema to get what amounts to an empty stack manifest from atmos's perspective to not generate an error.

yea, it's a problem now. The schema wants at least one section (I forgot if it supports empty file, no sections - need to recall)