We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
See above
Easier to populate stacks without having to dart between terraform variables and stack yaml
Integration with vscode
No response
The text was updated successfully, but these errors were encountered:
@dudymas is looking into something like this on the side. No ETA.
Sorry, something went wrong.
No branches or pull requests
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
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
The text was updated successfully, but these errors were encountered: