search

thoth-station / amun-api

Thoth's execution engine for inspecting quality, performance, and usability of software and software stacks in a cluster.
https://thoth-station.ninja/
GNU General Public License v3.0
8 stars 13 forks source link

Validate identifier length on the endpoint input #681

Open fridex opened 2 years ago

fridex commented 2 years ago

Is your feature request related to a problem? Please describe.

As a user of Amun API, I would like to make sure inspections are properly scheduled. If I make the identifier too long (which causes issues as pod names have a max length in kubernetes/openshift), the inspection I submit should be rejected with an appropriate error.

fridex commented 2 years ago

/label good-first-issue

sesheta commented 2 years ago

@fridex: The label(s) /label good-first-issue cannot be applied. These labels are supported: community/discussion, community/group-programming, community/maintenance, community/question, deployment_name/ocp4-stage, deployment_name/ocp4-test, deployment_name/moc-prod, hacktoberfest, hacktoberfest-accepted, kind/cleanup, kind/demo, kind/deprecation, kind/documentation, kind/question, sig/advisor, sig/build, sig/cyborgs, sig/devops, sig/documentation, sig/indicators, sig/investigator, sig/knowledge-graph, sig/slo, sig/solvers, thoth/group-programming, thoth/human-intervention-required, thoth/potential-observation, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, triage/accepted, triage/duplicate, triage/needs-information, triage/not-reproducible, triage/unresolved, lifecycle/submission-accepted, lifecycle/submission-rejected

In response to [this](https://github.com/thoth-station/amun-api/issues/681#issuecomment-1091906441): >/label good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

mayaCostantini commented 2 years ago

/remove-lifecycle stale /lifecycle frozen /sig user-experience

goern commented 2 years ago

/priority backlog