-
Notifications
You must be signed in to change notification settings - Fork 23
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
Unable to read ruleset on private git server with visual code #131
Comments
Issue persists in Extension version 1.0.0 |
Issue persists in Extension version 1.2.0 |
I am receiving a similar error, when my local ./spectral.yaml config extends a ruleset from an HTTPS URL that is self-signed by my corporate CA.
I have set the NODE_EXTRA_CA_CERTS environment variable to a path that contains the Root CA for the self-signed cert, which works from Spectral cli. I also added https://marketplace.visualstudio.com/items?itemName=pharndt.node-extra-ca-certs-vscode to VSCode, which I would expect to pick up that env variable. Sop far, none of these changes have affected the result - still the same error coming from the Spectral extension. |
On
|
Describe the bug
Unable to read ruleset on private git server with visual code
VSCODE SPECTRAL OUTPUT
An error occurred while validating document /home/USER/Documents/Bitbucket/PROJECT/folder/FILE_TO_LINT.yaml: Unable to read ruleset at /home/USER/Documents/Bitbucket/PROJECT/.spectral.yaml
To Reproduce
.spectral.yaml file
extends:
The bitbucket server is certified by an internal authority in my COMPANY with a ROOT_CA.
First step to debug:
spectral lint FILE_TO_LINT.yaml --ruleset https://bitbucket.COMPANY.CN/projects/TITLE/repos/LINTING/global-ruleset.yaml
request to https://bitbucket.COMPANY.CN/projects/TITLE/repos/LINTING/global-ruleset.yaml failed, reason: unable to get local issuer certificate
spectral lint FILE_TO_LINT.yaml --ruleset https://bitbucket.COMPANY.CN/projects/TITLE/repos/LINTING/global-ruleset.yaml
/home/USER/Documents/Bitbucket/PROJECT/folder/FILE_TO_LINT.yaml
10:12 warning XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
36:14 warning XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
89:18 warning XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
✖ 3 problems (0 errors, 3 warnings, 0 infos, 0 hints)
Expected behavior
Spectral in vscode should be able to accept ROOT_CA of a private COMPANY.
Environment:
The text was updated successfully, but these errors were encountered: