Add JSON Schema for Atmos Stack Manifests to the catalog

[aknysh]

what

• Add JSON Schema for Atmos Stack Manifests to the catalog

why

• Atmos Manifest JSON Schema can be used to validate Atmos stack manifests and provide auto-completion

references

• https://atmos.tools
• https://atmos.tools/reference/schemas
• https://atmos.tools/cli/commands/validate/stacks
• https://atmos.tools/core-concepts/stacks/validation
• https://atmos.tools/core-concepts/components/validation

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

[hyperupcall]

Thanks for the PR - is it possible to update "fileMatch": ["*.yaml", "*.yml"], to something less generic? Broad glob patterns can conflict with other schemas

[aknysh]

Thanks for the PR - is it possible to update "fileMatch": ["*.yaml", "*.yml"], to something less generic? Broad glob patterns can conflict with other schemas

@hyperupcall thanks for reviewing.
Atmos manifests are YAML files, they can be defined in any folder in a repo.
They can have any names.
I'm not sure if there is less generic definition of it since an infrastructure can have hundreds of Atmos stack manifests all with different names and location.

An Atmos Manifest is not a single configuration file, it's a set of files to define configurations for the entire infrastructure. For example, on AWS, the configurations for all Terraform components for all Organizations, Organizational Units, accounts and regions - can be many hundreds of Atmos manifest YAML files.

Very similar to how you'd define many Kubernetes manifests (in YAML) for a Kubernetes cluster.

Can we not specify fileMatch at ll?

[hyperupcall]

Ah I see - if I remember correctly, in the case of Kubernetes, i don't think it's uncommon files in places that match ["**/kubernetes/**/*.yml", "**/kustomize/**/*.yml"] (which would be acceptable fileMatches). If there is such a thing for Atmos (maybe "**/atmos/**/*.yml"? ), then that could work. If not, then you can always specify fileMatch as an empty array and I can merge without trouble.

[aknysh]

Ah I see - if I remember correctly, in the case of Kubernetes, i don't think it's uncommon files in places that match ["**/kubernetes/**/*.yml", "**/kustomize/**/*.yml"] (which would be acceptable fileMatches). If there is such a thing for Atmos (maybe "**/atmos/**/*.yml"? ), then that could work. If not, then you can always specify fileMatch as an empty array and I can merge without trouble.

@hyperupcall thank you.
Since Atmos manifests can be in any folder in any location, I've made fileMatch an empty array.
Appreciate all your help.

[hyperupcall]

sounds good! thanks