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

Show users data plane details and split up cidr blocks #1474

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

travjenkins
Copy link
Member

Issues

#1470

Changes

1470

  • Split apart the IPv4 and IPv6 in the cidr block arrays
  • Allow user to select which version to see/copy
  • Save off selection to local storage
  • Show all users the Data Planes section in admin

Tests

Manually tested

  • scenarios you manually tested

Automated tests

  • unit testing covered

Playwright tests ran locally

  • Admin
  • Captures
  • Collections
  • HomePage
  • Login
  • Materialization

Screenshots

Admin table public ipv4

image

Admin table public ipv6

image

Config shows ipv4

image

config showing ipv6

image

Keeping which option they chose in local storage
Using component to render CIDR Blocks
{hasSupportRole ? (
<Stack>
<Divider sx={{ mt: 2, mb: 4 }} />
<Stack>
Copy link
Member Author

Choose a reason for hiding this comment

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

We'll just always show to users now

Copy link
Member Author

Choose a reason for hiding this comment

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

Previously rendering cidr blocks was simple. This isn't too complex but best to keep it in a single place since we render these in the table and the config forms.

Some stuff is hardcoded - but I think it is fine since IPs do not change too often

Comment on lines 16 to 20
const [defaultDataPlane, setDefaultDataPlane] =
useLocalStorage<DataPlaneScopes>(
LocalStorageKeys.ADMIN_DATAPLANE_CHOICE,
defaultOption
);
Copy link
Member Author

Choose a reason for hiding this comment

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

Trying to make the UX better and not make users have to constantly switch between public and private. Eventually - this should be a setting stored with the select tenant.

@@ -13,7 +13,8 @@ export const JsonForms: Record<string, string> = {
'dateTimePicker.picker.footer': `Timezone: UTC`,
'datePicker.button.ariaLabel': `Open date picker for {label}`,
'informational.sshEndpoint.title': `All Estuary traffic comes from a group of IPs that can be whitelisted:`,
'informational.sshEndpoint.ip': `34.121.207.128, 35.226.75.135, 34.68.62.148`,
'informational.sshEndpoint.ipv4': `34.121.207.128, 35.226.75.135, 34.68.62.148`,
'informational.sshEndpoint.ipv6': `does not support IPv6`,
Copy link
Member Author

Choose a reason for hiding this comment

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

Very rare this would ever hit for something not related to the public data plan - but still kept the message open ended.

@@ -13,7 +13,8 @@ export const JsonForms: Record<string, string> = {
'dateTimePicker.picker.footer': `Timezone: UTC`,
'datePicker.button.ariaLabel': `Open date picker for {label}`,
'informational.sshEndpoint.title': `All Estuary traffic comes from a group of IPs that can be whitelisted:`,
'informational.sshEndpoint.ip': `34.121.207.128, 35.226.75.135, 34.68.62.148`,
'informational.sshEndpoint.ipv4': `34.121.207.128, 35.226.75.135, 34.68.62.148`,
Copy link
Member Author

Choose a reason for hiding this comment

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

Only the key changed

@travjenkins travjenkins marked this pull request as ready for review February 25, 2025 16:52
@travjenkins travjenkins requested a review from a team as a code owner February 25, 2025 16:52
@travjenkins travjenkins changed the title Travjenkins/feature/show data plane table Show users data plane details and split up cidr blocks Feb 25, 2025
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.

1 participant