redhat-developer / redhat-developer/vscode-yaml
source.toolkit.fluxcd.io manifest with name prometheus.yaml error: Request vscode/content failed unexpectedly without providing any details.YAML(768)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
i have a manifest file name: prometheus.yaml and , by default, the extension point to schema https://json.schemastore.org/prometheus.json but it's not my case because this a manifest relate to kind HelmRepository.
This is the content:
cat prometheus.yaml
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
name: prometheus
spec:
interval: 24h0m0s
url: https://prometheus-community.github.io/helm-charts
Expected Behavior
the file contents are not marked as error
Current Behavior
Unable to load schema from 'https://json.schemastore.org/prometheus.json': Request vscode/content failed unexpectedly without providing any details.YAML(768)
Steps to Reproduce
- create a file with name : prometheus.yaml
- add this content or any others type of contents like:
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
name: prometheus
spec:
interval: 24h0m0s
url: https://prometheus-community.github.io/helm-charts
- Open the file in vscode and see the error
Environment
- [ X] Windows
- Mac
- [ X] Linux
- other (please specify)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the VS Code YAML extension's schema selection for the manifest named prometheus.yaml, using the reported SchemaStore URL and HelmRepository content as the reproduction. Done means this Kubernetes manifest no longer loads prometheus.json or reports the YAML(768) schema error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, vscode
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100