redhat-developer / redhat-developer/vscode-yaml
Supports Circle CI Pipeline values and parameters in `resource_class`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Is your enhancement related to a problem? Please describe.
No.
Describe the solution you would like
Do not output error messages when using Pipeline values and parameters with resource_class in .circleci/config.yaml.
https://circleci.com/docs/pipeline-variables/
Currently, when the following is specified:
jobs:
job1:
resource_class: << pipeline.parameters.resource-class >>
the following error message is shown.
Value is not accepted. Valid values: "small", "medium", "medium+", "large", "xlarge", "2xlarge", "2xlarge+", "arm.medium", "arm.large", "arm.xlarge", "arm.2xlarge".
Describe alternatives you have considered
Support the use of Pipeline values and parameters with resource_class.
Additional context
N/A
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 by reproducing the validation error with the example in .circleci/config.yaml and read CircleCI's pipeline variables documentation. Trace how resource_class values are checked, then verify that a pipeline parameter there no longer produces the listed-value error while literal resource classes remain validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100