-
Notifications
You must be signed in to change notification settings - Fork 875
feat: display provisioner jobs and daemons for an organization #16532
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
Conversation
…r-provisioners
…r-provisioners
…r-provisioners
…r-provisioners
…r-provisioners
@jaaydenh I would appreciate a first review on this PR. |
@BrunoQuaresma can you include in the description the issue this PR is resolving? Trying to understand the reason for the name change OrganizationProvisionersPage to just ProvisionersPage? Is the provisioners page now meant to be used outside organizations as well? |
|
Ya, the issue is that most of the components have the Organization Prefix so its more confusing if its only removed for some of them. |
…r-provisioners
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.
Didn't find anything major here – just had a few recommendations. Not approving because I don't know how much more needs to be added to get the PR out of the draft stage, but I can do another pass once the PR goes live
site/src/pages/OrganizationSettingsPage/ProvisionersPage/CancelJobButton.tsx
Outdated
Show resolved
Hide resolved
parameters: { | ||
chromatic: { disableSnapshot: true }, | ||
}, |
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.
Is this what we're doing for any frontend testing that's more involved? Wondering if React Testing Library still ever makes sense for our components, or if we can offload everything to Storybook
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.
Is this what we're doing for any frontend testing that's more involved?
In this case, I only want to test the behavior since a snapshot is not valuable at all. I'm guessing disabling unnecessary snapshots can make our test suite faster.
Wondering if React Testing Library still ever makes sense for our components, or if we can offload everything to Storybook
With interaction tests, I think we can offload everything to Storybook - just a guess, but I think storybook uses testing library under the hood.
site/src/pages/OrganizationSettingsPage/ProvisionersPage/CancelJobButton.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/OrganizationSettingsPage/ProvisionersPage/CancelJobConfirmationDialog.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/OrganizationSettingsPage/ProvisionersPage/ProvisionerDaemonsPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/OrganizationSettingsPage/ProvisionersPage/ProvisionerDaemonsPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/OrganizationSettingsPage/ProvisionersPage/ProvisionerJobsPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/OrganizationSettingsPage/ProvisionersPage/ProvisionerDaemonsPage.tsx
Show resolved
Hide resolved
site/src/pages/OrganizationSettingsPage/ProvisionersPage/ProvisionerDaemonsPage.tsx
Outdated
Show resolved
Hide resolved
Actually looking at this again, I agree it does make more sense to move the Provisioners files to their own folder and removing the prefix. |
@Parkreiner @jaaydenh I'm planning to add the storybook tests for the pages after getting this merged on main and having a QA from Christin and Bartek so I can avoid wasting time on testing something that is not what we want. |
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. Let's play with it in dogfood!
Nice job, Bruno 👍
@@ -1,48 +0,0 @@ | |||
import { buildInfo } from "api/queries/buildInfo"; |
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.
Perhaps I'm missing some context, could you explain why are we removing these pages? Will they be replaced now?
PS. It would be convenient to add Changes: to the PR description.
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.
Yes, they will be replaced.
Jobs:

Figma Link
Daemons:

Figma Link
Closes #15192 and Closes #15193