Skip to content

fix: use multi-org settings layout even if not licensed #14215

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

Merged
merged 7 commits into from
Aug 9, 2024

Conversation

code-asher
Copy link
Member

@code-asher code-asher commented Aug 8, 2024

Originally, I had it using the multi-org layout if the multi-org experiment was enabled AND the feature was entitled.

However, we actually want to use the new layout even for single-org deployments, so I changed it; we now use the new layout ONLY when the multi-org experiment is enabled, even if the license is not entitled to the feature. In the future, when the experiment is over, the multi-org layout will be the default and we can delete and permanently redirect the old views.

However, this means that you could see the create org page and not have the ability to use it, so I added our standard license badges to that page. So if you go there and do not have a license, you now see the disabled badge.

We did not have a badge for the premium license, which is what orgs requires, so I added it. I am not 100% sure if the wording is right.

Then, the badges looked a bit janky with PageHeader so I moved the header used on all the other settings pages to the components directory and used it instead of PageHeader. Then I used it on the rest of the org pages as well for consistency (create org, edit org, members, and groups). It also brings some cohesiveness with the other settings pages, since they are all on the same sidebar and now these pages all use the same header style. Doing this also got rid of some extra padding.

So in summary:

  1. Should always use the new settings layout even if not licensed (as long as multi-org experiment is on).
  2. Should see license info in the create org page.
  3. Various org pages should have headers consistent with the other settings pages.

Stacked on:

Copy link

alwaysmeticulous bot commented Aug 8, 2024

🤖 Meticulous spotted visual differences in 271 of 1324 screens tested: view and approve differences detected.

Last updated for commit 46a28e0. This comment will update as new commits are pushed.

@code-asher code-asher force-pushed the asher/multi-org-by-flag-only branch from 5bcc2f6 to fb933bd Compare August 8, 2024 00:35
@code-asher code-asher changed the base branch from main to asher/move-audit-log August 8, 2024 00:35
@code-asher code-asher force-pushed the asher/multi-org-by-flag-only branch from fb933bd to b06663b Compare August 8, 2024 00:46
<PopoverPaywall
message="Organizations"
description="Organizations allow you to run a Coder deployment with multiple platform teams, all with unique use cases, templates, and even underlying infrastructure."
// TODO: No documentation link yet.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will make a note

args: {
message: "Black Lotus",
description:
"Adds 3 mana of any single color of your choice to your mana pool, then is discarded. Tapping this artifact can be played as an interrupt.",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOL, someone is playing too much Magic 😆

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choosing the MVP of cards

Copy link
Collaborator

@BrunoQuaresma BrunoQuaresma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good to me. I just would make the header less bold like we do for the workspace proxies settings.

Screenshot 2024-08-08 at 10 41 21

@Emyrk
Copy link
Member

Emyrk commented Aug 8, 2024

However, this means that you could see the create org page and not have the ability to use it, so I added our standard license badges to that page. So if you go there and do not have a license, you now see the disabled badge.

Sweet!

@code-asher
Copy link
Member Author

It looks good to me. I just would make the header less bold like we do for the workspace proxies settings.

Right now the workspace proxies page is the only one that is not bold, so it looks like the odd one out. Should we maybe change all of the pages to not be bold?

@BrunoQuaresma
Copy link
Collaborator

@code-asher I think so but I will leave this up to you

@code-asher code-asher force-pushed the asher/move-audit-log branch 3 times, most recently from fdfe3ac to 39defe5 Compare August 9, 2024 06:32
Base automatically changed from asher/move-audit-log to main August 9, 2024 06:41
@code-asher
Copy link
Member Author

I think so but I will leave this up to you

Sounds good to me! I will push up another PR soon for this.

I added checks against the license but actually what we want is for
these views to become the default even when not licensed (once the
experimental flag is removed).
This will let us use it in the org settings pages, for a consistent
look.
@code-asher code-asher force-pushed the asher/multi-org-by-flag-only branch from b06663b to cde4095 Compare August 9, 2024 06:44
@code-asher code-asher force-pushed the asher/multi-org-by-flag-only branch from cde4095 to b31b68a Compare August 9, 2024 07:05
I am not sure if there is maybe a better place for this, but maybe this
is good enough.
It says "change", but there is nothing to change yet since this is a new
organization.
@code-asher code-asher force-pushed the asher/multi-org-by-flag-only branch from b31b68a to dd3a470 Compare August 9, 2024 07:06
@code-asher code-asher merged commit abbcffe into main Aug 9, 2024
30 checks passed
@code-asher code-asher deleted the asher/multi-org-by-flag-only branch August 9, 2024 07:29
@github-actions github-actions bot locked and limited conversation to collaborators Aug 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants