Anything that needs to be configured with YAML, and Kubernetes in particular.
I mean I get the whole Infrastructure as Code hype (although I have never witnessed or heard of a situation where an entire cluster needed to be revived from scratch), but it should be very possible to make a gui that writes the YAML for you.
I don’t want to memorize every possible setting and what it does and if someone makes a typo in the config (or in the white space, as it’s YAML) everything is borked.
Call me old-fashioned but the graphical ui of something like octopus deploy was a thousand times more user friendly imho.
I think it’s easy to make a generic YAML editor that all you need to do is to pass a “definitions” file that says all the possible options to show as a drop down or toggle etc.
A few IDEs already provide some help with YAML. Rider will tell you if you’ve screwed up the YAML for a GitHub Actions workflow, and possibly docker-compose as well
I think infrastructure as code is best utilized when paired with software testing and rapid deployment. It allows for a kind of granularity manual configuration doesn’t give you
Anything that needs to be configured with YAML, and Kubernetes in particular.
I mean I get the whole Infrastructure as Code hype (although I have never witnessed or heard of a situation where an entire cluster needed to be revived from scratch), but it should be very possible to make a gui that writes the YAML for you.
I don’t want to memorize every possible setting and what it does and if someone makes a typo in the config (or in the white space, as it’s YAML) everything is borked.
Call me old-fashioned but the graphical ui of something like octopus deploy was a thousand times more user friendly imho.
That UI is called VSCode
At the top of your
.yamlfile, you can set a JSON Schema. Example:# yaml-language-server: $schema=https://json.schemastore.org/prometheus.json scrape_configs: - job_name: caddy static_configs: - targets: - caddy:2019This way, you don’t have to memorize every possible setting and what it does and risk making a typo in the config. VSCode will just tell you.
I think it’s easy to make a generic YAML editor that all you need to do is to pass a “definitions” file that says all the possible options to show as a drop down or toggle etc.
That would be useful for many projects.
A few IDEs already provide some help with YAML. Rider will tell you if you’ve screwed up the YAML for a GitHub Actions workflow, and possibly docker-compose as well
I think infrastructure as code is best utilized when paired with software testing and rapid deployment. It allows for a kind of granularity manual configuration doesn’t give you