-
Notifications
You must be signed in to change notification settings - Fork 420
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
API rule violations in Triggers types #1271
Comments
Should we create an exception list or do we need to change the names? |
We might have to create an exception list for the names_match ones. We should fix the list_type_missing ones |
fwiw, I can't find a way to specify exceptions to rules. If I'm missing something, I'd love to know so I can change tektoncd/pipeline#4402 to ignore the mismatched names. Oh, and I'll happily take this on as well. =) |
This is part of tektoncd#1271 - `names_match` violations still need to be dealt with. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
This is part of #1271 - `names_match` violations still need to be dealt with. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Hmmm...I had found this https://github.com/kubernetes/kubernetes/tree/36981002246682ed7dc4de54ccc2a96c1a0cbbdb/api/api-rules though I'm not sure if this is something directly supported by the tool or if they wrote something on top to ignore the specific violations |
Yeah, looks like it's custom. We can probably rig that up ourselves, I'll take a look. |
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix #1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
This is part of tektoncd#1271 - `names_match` violations still need to be dealt with. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
This is part of tektoncd#1271 - `names_match` violations still need to be dealt with. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
This is part of tektoncd#1271 - `names_match` violations still need to be dealt with. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
And fix tektoncd#1271 along the way by using the same scripting as in tektoncd/pipeline#4402 to ignore API rule violations for `name_match` which already exist. Any new mismatch will cause an error. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Expected Behavior
Triggers should have 0 API violations
Actual Behavior
Running openapi-gen results in the following API violations:
Steps to Reproduce the Problem
go run k8s.io/kube-openapi/cmd/openapi-gen \ --input-dirs ./pkg/apis/triggers/v1beta1,knative.dev/pkg/apis,knative.dev/pkg/apis/duck/v1beta1 \ --output-package ./pkg/apis/triggers/v1beta1 -o ./ \ --go-header-file hack/boilerplate/boilerplate.go.txt
The text was updated successfully, but these errors were encountered: