Open iwahbe opened 2 years ago
Note additional detail on https://github.com/pulumi/pulumi-lsp/issues/77
Notably, it appears you get an error if you have both installed:
Note that an extension may be disabled on a per-workspace basis, but it isn't clear to me whether the "Disable Red Hat YAML" button disables for this workspace or globally.
Also, the current arrangement of having the Pulumi LSP be a sub-extension of the main extension allows the user to disable the LSP without losing the debugging or ESC functionality.
Some points about the Red Hat YAML extension:
A note from @ringods related to this:
the Github Actions extension also manages YAML files but doesn't conflict with Redhat YAML. Looking into their
package.json
, they register a separate language and limit the scope to some file patterns: https://github.com/github/vscode-github-actions/blob/44facd0a4a4cbb64c0eead90df04195028e10063/package.json#L33-L49Looking at the docs for
contributes.languages
extension point, I think we will have to experiment with filename patterns and/orfirstline
option for our extension to be picked up as the language instead of being treated as generic YAML by the Redhat extension. https://code.visualstudio.com/api/references/contribution-points#contributes.languages
Any update? 🤔
We are using GitHub Actions, Pulumi, and K8s daily, so I need to install all three extensions.
The K8s extension requires Redhat YAML, so if you disable it, the k8s extension won't work.
Pulumi conf files start with Pulumi.ENV.yaml
, so I don't think enabling it will be hard based on the file name.
When I open a Pulumi file, the language Mode is set to YAML
, for us, we have three environments, dev, test, and prod
but when I open Pulumi.test.yaml
I see the following error:
The only thing worked for us was adding this to the settings:
"files.associations": {
"Pulumi.yaml": "pulumi-esc",
"Pulumi.*.yaml": "pulumi-esc"
}
Hello!
Issue details
Affected area/feature