Integration with IDEs

[nitrocode]

Describe the Feature

I'd love if I could get input vars in stack catalogs to populate

I recently got this working in vscode for cloud custodian and it would be really cool to see it working with atmos

https://cloudcustodian.io/docs/quickstart/index.html#editor-integration

For atmos, the commands might be

atmos schema --json > schema.json

And these commands would probably need to be rerun on new input vars in components or new import catalogs or new components

Expected Behavior

See above

Use Case

Easier to populate stacks without having to dart between terraform variables and stack yaml

Describe Ideal Solution

Integration with vscode

Alternatives Considered

No response

Additional Context

No response

[osterman]

@dudymas is looking into something like this on the side. No ETA.

[osterman]

So we documented how this is supported today. Do you think it's worth creating a separate issue to provide a command to conveniently retrieve the schema as well?

Since atmos now supports remote schemas, and VS Code et. al support remote schemas, having a local schema is less valuable.

• Add support for remote validation schemas #731
• Set Default Schema to Remote Schema #777

[osterman]

Check out our new documentation: https://atmos.tools/core-concepts/projects/setup-editor