Doc updates for egress IP addresses #1566
Conversation
|
site/docs/concepts/connectors.md
Outdated
| @@ -286,7 +288,7 @@ In some cases, your source or destination endpoint may be within a secure networ | |||
| to allow direct access to its port due to your organization's security policy. | |||
|
|
|||
| :::tip | |||
| If permitted by your organization, a quicker solution is to whitelist the Estuary IP address, `34.121.207.128`. | |||
| If permitted by your organization, a quicker solution is to whitelist the Estuary IP addresses, `34.121.207.128, 35.226.75.135, 34.68.62.148`. | |||
There was a problem hiding this comment.
I think from a UI/UX aspect breaking these up into a small list that has one IP per line could make sense. However, that would make them a lot harder to copy/paste the list.
From an ops perspective would keeping these as a comma separated list make it easier to configure on the client's system?
There was a problem hiding this comment.
This is actually kind of tricky. I moved these into a code block for where it's in a tool tip and it looks like the attached.
In other cases, I just added a : so it was clear a list was coming. Trying to make a UL in markdown for other cases was very visually jarring. The other option was to put something like
34.121.207.128, 35.226.75.135 and 34.68.62.148
for proper English, but the flow on that is gross too.
There was a problem hiding this comment.
Looks good to me and follows the pattern up above... though that is kinda different given you really should copy the value.
skord
force-pushed
the
mdanko/ip-addr-doc-updates
branch
from
be56166
to
c7fc51a
Compare
committing for preview formatting
skord
force-pushed
the
mdanko/ip-addr-doc-updates
branch
from
c7fc51a
to
3d0c6aa
Compare
Description:
This just updates docs to reflect the three current possible egress IP's for Flow.
Workflow steps:
(How does one use this feature, and how has it changed)
Documentation links affected:
It's all documentation, so every doc in the commit.
This change is