-
Notifications
You must be signed in to change notification settings - Fork 103
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
add sort and filter to admin/workspaces#list-all-workspaces #641
Conversation
453afa8
to
b29ee76
Compare
d4b068c
to
e8d58eb
Compare
e8d58eb
to
6ebe908
Compare
8c908b8
to
11c3743
Compare
|
||
require.NoError(t, err) | ||
require.NotEmpty(t, wl.Items) | ||
assert.Equal(t, wl.Items[0].CurrentRun.Status, RunApplied) |
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.
Oh, now that I think this through an extra step, this is fine and doesn't need to be changed to an assert.Contains
with our run. I got all turned around! But because the filter is limiting runs to the RunApplied status, the first run definitely has to be in status RunApplied, even if it's not the run we created. 👍🏼
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.
Ok!
Reminder to the contributor that merged this PR: if your changes have added important functionality or fixed a relevant bug, open a follow-up PR to update CHANGELOG.md with a note on your changes. |
Description
The Admin Workspace API includes a sort and filter feature. There was a request to expose this in go-tfe.
Testing plan
name
orcurrent-run.created-at
run status
External links
API Docs
Output from tests
Including output from tests may require access to a TFE instance. Ignore this section if you have no environment to test against.