Erik Osterman (CEO @ Cloud Posse)
Erik Osterman (CEO @ Cloud Posse)
We just started getting this as well. https://github.com/cloudposse/atmos/actions/runs/9664474935
@aknysh what do you think about making this the default location for the schema? That way `atmos validate` always works, even if no schema installed locally.
> In which case we need to allow the user to opt-out I think they can set the path to `/dev/null` to "opt out" =) But at a very least,...
@haitham911 also please update docs here: https://atmos.tools/core-concepts/validate/json-schema with how to specify remote schemas
@haitham911 please post screenshot of this in action. Please confirm that using files as well as remote URLs both work. Also, this PR is conflicted.
@haitham911 we haven't set a default schema. If you run: `atmos describe config`, you'll see JSON schema is not set: ``` "schemas": { "jsonschema": {}, "cue": {}, "opa": {}, "atmos":...
Here's what we should aim to replicate with `--everything` https://github.com/cloudposse/atmos/blob/main/demo/screengrabs/scripts/demo-stacks/.demo.rc#L17-L22 Of this, I think we're missing also the `*.tfvar.json` and `*.tf.json` files. Also, if no component is passed, can we...
Also, please post screenshots of this in action.
Please output relative paths
@haitham911 please resolve conflicts