Skip to content
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

fix(ui): remove mentions of TSM-specific limits for Serverless users #6889

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mavarius
Copy link
Collaborator

@mavarius mavarius commented May 15, 2024

This PR removes the mention of TSM-specific limits for Serverless users.
image

Checklist

Authors and Reviewer(s), please verify the following:

  • A PR description, regardless of the triviality of this change, that communicates the value of this PR
  • Well-formatted conventional commit messages that provide context into the change
  • Feature flagged, if applicable

@mavarius mavarius requested a review from a team as a code owner May 15, 2024 19:49
Copy link
Contributor

@wdoconnell wdoconnell left a comment

Choose a reason for hiding this comment

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

Couple of questions - main one of note was which of TSM versus IOx the "unlimited tasks, unlimited alert checks" messaging applies to.

@@ -104,6 +104,15 @@ export const OrgLimits: FC = () => {
)
}

// The 'dashboards', 'tasks', 'checks', and 'rules' limits are not applicable to orgs using IOx.
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we put this check at the beginning of the return/render, since it looks like it supersedes the other rules about which limits should be displayed?

cardinality
</li>
<>
<li>Unlimited dashboards</li>
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the absence of limits (no task limit, no alert limit, no pagerduty limit) only apply to TSM?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Only TSM should get this message, I can see how that isn't very clear. I can restate it as a ternary on orgUsesIOx.

<li>Unlimited dashboards</li>
<li>Unlimited tasks</li>
<li>Unlimited alert checks and notification rules</li>
<li>HTTP and PagerDuty notifications</li>
{!orgUsesIOx && (
Copy link
Contributor

Choose a reason for hiding this comment

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

Same question as above.

@wdoconnell
Copy link
Contributor

@mavarius Do you need anything else on this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants