Incorrect `resource_class` validation when using self-hosted runner

[BMeach]

Hello all, I recently started using CircleCI and I am using on-prem self-hosted runners. When I added the VSCode extension it said that my resource_class was invalid, yet when I did Validate current configuration file it says its valid and the workflow works without issues. I think there needs to be a way to detect when using a self hosted runner in the resource class.

When I change the namespace it seems to know what is and is not valid for the namespace but it is determined that my is invalid. Below is the error message I get from VSCode.

Value is not accepted. Valid values: "small", "medium", "medium+", "large", "xlarge", "2xlarge", "2xlarge+", "arm.medium", "arm.large", "arm.xlarge", "arm.2xlarge".

[loderunner]

Hi @BMeach!

Thanks for using the VS Code extension, and providing us with feedback.

Can you tell us which extension is giving you this validation error? VS Code adds the extension identifier to the error tooltip.

For example, this error—that seems similar to yours—is generated by the Red Hat YAML extension.

By contrast, here is a diagnostics message generated by the CircleCI language server.

The Red Hat YAML extension relies on SchemaStore to validate many formats of JSON and YAML. While we do contribute to SchemaStore to support CircleCI config files as best we can, we ultimately aren't in control of these 3rd-party extensions.

---

If you could provide us with an example config file to reproduce your issue, we'll be sure to look into ensuring that SchemaStore supports your case.

[BMeach]

You're exactly correct. I apologize for the oversight, the error is from yaml-schema. I will add the CircleCI to an exclude file for the YAML validator.

[loderunner]

No worries. If you can, please do provide us with a YAML file to reproduce your bug, and we'll try to contribute to SchemaStore to support your case.

[BMeach]

Here is an example of the lines that I was getting errors on.

version: 2.1

executors:
  management:
    docker:
      - image: hashicorp/terraform:latest
    resource_class: my-org/terraform-k3s-cluster-infrastructure
  test:
    docker:
      - image: hashicorp/terraform:latest
    resource_class: my-org/terraform-k3s-cluster-infrastructure

Here are all of the VSCode extensions I have installed.

• ms-python.python
• ms-python.vscode-pylance
• hashicorp.hcl
• hashicorp.terraform
• ms-vscode.azure-account
• ms-azuretools.vscode-azureterraform
• github.vscode-github-actions
• GitHub.copilot
• GitHub.copilot-chat
• GitHub.vscode-pull-request-github
• eamodio.gitlens
• DavidAnson.vscode-markdownlint
• redhat.vscode-yaml
• circleci.circleci

Here is a screenshot of the error in VSCode

[loderunner]

Thanks!

I'll be closing the issue in this repo, since this is a problem with the schema in SchemaStore. I'm tracking the issue on our internal board, and we'll try to contribute the public schema as soon as possible.

[BMeach]

Thank you for the quick help!