-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
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
The Ansible "!vault" tag should be known #194
Comments
thanks for reporting the issue. Yaml validation is based on yaml language server, it has no knowledge of ansible specific syntax including vault. will try to look at if there's way to suppress specific error, which i suspect might not. |
The vscode yaml project has a solution to this using custom tags, but this ansible extension overrides their solution. Are you able to implement their suggestion into this project? |
Simply adding After installing the "redhat.vscode-yaml" extension, the "Unknown configuration setting" error is gone, but the "unknown tag <!vault>" persists. |
@oncipriani, yep. If you disable the vscode-ansible extension the "unknown tag" error will go, so some part of the vscode-ansible extension is overriding the functionality from the vscode-yaml extension. |
@Taoquitok, I removed the vscode-ansible extension. The error was more annoying than the benefits the extension provided. Thank you. |
@oncipriani before we support custom tags, you could disable the validation by setting |
Wouldn't this disable all validation? This extension is a real life saver for me, since it helps me write faster, a lot faster, than normal. Disabling the validation would break everything for me. Sorry to nag, but we got any status of when we can either support this tag, or if we will be able to use the Thanks! |
@f-eric, I believe the idea for now is to use |
@kpocius Thanks for the quick reply! I suppose you're right. I'll switch plugin when working with these specific files. And thanks again, for leading me the right way. 🙂 |
Actually, I just configured the |
@f-eric Configuring Setting My Visual Studio version information (running on Windows 10):
|
Hi. This an annoying one. What do you need to fix it? Can I help? |
hi @snoopotic you could disable the validation by setting "ansible.validation": false to disable the validation. |
@yungezz but isn't one main purpose of the ansible plugin to HAVE validation? So disabling is a workaround. |
@yungezz this is fixed in the language server, see: |
I am having the same issue - even with "!valut" in my yaml.customTags setting. |
For new readers, the workaround I'm using to get rid of false errors when using the <!vault> tag:
|
Just want to chime in and say this affects me as well. |
add to @Melvin-mlp 's suggestion:
|
Issue Type: Bug
When using
ansible-vault encrypt_string
to create a single encrypted variable and pasting it into any YAML file, Visual Studio Code complains with the following message:Extension version: 0.5.1
VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T16:17:45.060Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: