-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Allow wildcard for Evaluations API #13530
Allow wildcard for Evaluations API #13530
Conversation
Ember Asset Size actionAs of 75e70c0 Files that got Bigger 🚨:
Files that stayed the same size 🤷:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we need to make any edits client-side, I would suspect we'd need to check the formatting logic in generateFilterExpression. However, the tests assert on how user actions impact the request we're sending and the default request we send when we enter the view. I'd love to learn if we wrote those tests and the formatting logic incorrectly.
I highly recommend reading that filtering logic and the tests to see if we got something wrong. But, I believe @mikenomitch pointed the real issue out 12918 and we should ask @lgfa29 to prioritize this issue in the backlog.
Thankfully, @lgfa29 is also an expert web developer and can provide insights if I'm wrong here.
@@ -35,7 +35,7 @@ export default class EvaluationsController extends Controller { | |||
'currentEval', | |||
'pageSize', | |||
'status', | |||
'qpNamespace', | |||
{ qpNamespace: 'namespace' }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blocking
: I don't think this resolves the issue. This sets the alias of the query parameter in the URL. But, this shouldn't impact formatting the request in the route.
If we need to make any edits, I would suspect we'd need to check the formatting logic in generateFilterExpression
. However, the tests assert on how user actions impact the request we're sending and the default request we send when we enter the view. I'd love to learn if we wrote those tests and the formatting logic incorrectly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This impacts the initial query that our /evaluations route makes; it is making the (currently bugged, hopefully fixed by this PR) call to *
under all circumstances currently.
That's overeager for what a user might be looking for, though, and inconsistent with how other routes that are namespace-aware (volumes, jobs, which only fetch according to your namespace on load) operate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's your call to make. We can totally adopt that pattern, but that's an undocumented behavior we'd have to load into our mental models. We specifically designed this to set namespace to *
when entering this view. I could see the mental baggage of keeping this type of knowledge in our heads with an Ember Routing API change.
It's good UX to have. So totally your call, I'll support whatever you decide. I'll update my review on this PR to approved and let you handle this how you think is best.
Ember Test Audit comparison
|
#12918 could have contributed to this error if the UI requests a specific eval using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I left some comments on the API bits in #13552 but nothing blocking.
39f7c54
to
9f4095d
Compare
9f4095d
to
81ab4d9
Compare
81ab4d9
to
c5d251a
Compare
Apply the same verification process as in job, allocs and scaling policy list endpoints to handle the eval list when using an ACL token with limited namespace support but querying using the `*` wildcard namespace.
c5d251a
to
fe3a7f6
Compare
599df8c
to
45642bd
Compare
Evals have a unique UUID as ID, but when querying them the Nomad API still expects a namespace query param, otherwise it assumes `default`.
45642bd
to
75e70c0
Compare
7f8abfd
to
75e70c0
Compare
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
UI:
namespace=<namespace>
query parameter was not being observed by the Evaluations routeRemove persistence of the passed namespace (from jobs, volumes, etc.)moved to Remove namespace cache #13679API:
*
namespaceAllNamespacesSentinel
before sendingErrPermissionDenied