Closed Enigo closed 2 months ago
Thanks for the report @Enigo. We are aware that Yaml validation could sometime run into a conflict. There is an ongoing effort to make it smoother, we'll let you know when it's ready.
thanks @ivanporty are you also considering to split this plugin into smaller ones or have an option to only load some modules?
Yes, we might be making features to be available on demand rather than enabling them all together - do you think such approach would fit your needs? I.e. you may enable Cloud databases only and Cloud Run, but don't see/use other features until enabling them.
Absolutely! That's especially important if/when you add more services to the plugin. I would personally prefer to have multiple smaller plugins per service instead of one huge one with option to disable parts of it. But I imagine that's harder to maintain
In the latest release (24.4.2
), we have added the ability to disable YAML support through the settings (Settings > Tools > Google Cloud Code > Kubernetes). docs here
Good day! See the screenshot:
The error is
unknown tag <!Split>
and many more of those custom AWS CF. Yeah, we have multiple clouds atm.Expected Behavior
Don't interfere with the existing linting - I'm using cfn-lint plugin for this
Actual Behavior
It seems to overrides what other plugins are doing (?)
Additional Information
What would make the most sense for this plugin imo is to have a modularity. E.g. I don't actually need k8s related things on my project, only Cloud DB. But I'm forced to get everything instead. Not particularly user-friendly.
I could also somewhat disable it by setting YAML file matcher to something that doesn't match any yaml files.