Skip to content

Commit 2e4fdfa

Browse files
[BYOIP, CF4SaaS] Implement DashButton component (#24864)
* Replace Address Maps occurrences * Replace Notifications occurrence * Add DashButton to only account-level step in CF4SaaS
1 parent 7937bc6 commit 2e4fdfa

File tree

5 files changed

+49
-36
lines changed

5 files changed

+49
-36
lines changed

src/content/docs/byoip/address-maps/setup.mdx

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
label: Setup
77
---
88

9-
import { GlossaryTooltip, APIRequest } from "~/components";
9+
import { GlossaryTooltip, APIRequest, DashButton } from "~/components";
1010

1111
Consider the sections below to learn how to set up address maps.
1212

@@ -20,25 +20,29 @@ To avoid any errors if you have [static IPs](/byoip/concepts/static-ips/), Cloud
2020

2121
If you are using BYOIP instead, refer to the following steps:
2222

23-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
24-
2. Go to **IP Addresses** > **Address Maps**.
25-
3. Select **Create an address map**.
26-
4. Choose the scope of the address map.
27-
5. Add the zones and IP addresses that you want to map.
28-
6. Name your address map.
29-
7. Review the information and select **Save and Deploy**.
23+
1. In the Cloudflare dashboard, go to the **Address Maps** page.
24+
25+
<DashButton url="/?to=/:account/ip-addresses/proxy-ips" />
26+
27+
2. Select **Create an address map**.
28+
3. Choose the scope of the address map.
29+
4. Add the zones and IP addresses that you want to map.
30+
5. Name your address map.
31+
6. Review the information and select **Save and Deploy**.
3032

3133
:::note
3234
Creating an address map does not automatically change DNS configuration. DNS responses only begin to change when a zone or account is added to a map. Additionally, address maps that are not yet enabled will not take effect in DNS responses.
3335
:::
3436

3537
## Manage address maps
3638

37-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
38-
2. Go to **IP Addresses** > **Address Maps**.
39-
3. Go to your address map and select **Review**.
40-
4. Edit your address map.
41-
5. Review the information and select **Save**.
39+
1. In the Cloudflare dashboard, go to the **Address Maps** page.
40+
41+
<DashButton url="/?to=/:account/ip-addresses/proxy-ips" />
42+
43+
2. Go to your address map and select **Review**.
44+
3. Edit your address map.
45+
4. Review the information and select **Save**.
4246

4347
:::note
4448
You can also enable, disable, and delete address maps. This will likely change the IP addresses used for your zones.

src/content/docs/byoip/route-leak-detection.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66

77
---
88

9-
import { AvailableNotifications } from "~/components"
9+
import { AvailableNotifications, DashButton } from "~/components"
1010

1111
Route Leak Detection protects your routes on the Internet by notifying you when your traffic is routed somewhere it should not go, which could indicate a possible attack. Route Leak Detection also reduces the amount of time needed to mitigate leaks by providing you with timely notifications.
1212

@@ -18,8 +18,11 @@ Cloudflare detects route leaks by using several sources of routing data to creat
1818

1919
You must be a user who has brought your own IP address to Cloudflare, which includes Magic Transit, Spectrum, and WAF users. Only prefixes advertised by Cloudflare qualify for Route Leak Detection.
2020

21-
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
22-
2. Select **Notifications** > **Add**.
21+
1. In the Cloudflare dashboard, go to the **Notifications** page.
22+
23+
<DashButton url="/?to=/:account/notifications" />
24+
25+
2. Select **Add**.
2326
3. Locate **Route Leak Detection** from the list > **Select**.
2427
4. Enter a name and description for the notification.
2528
5. Enter one or more email addresses to receive the notifications.

src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ import {
1414
TabItem,
1515
Tabs,
1616
GlossaryTooltip,
17+
DashButton,
1718
} from "~/components";
1819

1920
With [service bindings](/byoip/service-bindings/), CDN[^1] customers using BYOIP can take the same prefix they have onboarded to Cloudflare and use it to selectively route traffic on a per-IP address basis to [Spectrum](/spectrum/)[^2], or vice versa. This means:
@@ -98,13 +99,15 @@ If you need to map only specific subdomains (and not all proxied DNS records) to
9899
<Tabs syncKey="dashPlusAPI">
99100
<TabItem label="Dashboard" no-code="true">
100101

101-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
102-
2. Go to **IP Addresses** > **Address Maps**.
103-
3. Select **Create an address map**.
104-
4. Choose the scope of the address map.
105-
5. Add the zones and IP addresses that you want to map.
106-
6. Name your address map.
107-
7. Review the information and select **Save and Deploy**.
102+
1. In the Cloudflare dashboard, go to the **Address Maps** page.
103+
104+
<DashButton url="/?to=/:account/ip-addresses/proxy-ips" />
105+
106+
2. Select **Create an address map**.
107+
3. Choose the scope of the address map.
108+
4. Add the zones and IP addresses that you want to map.
109+
5. Name your address map.
110+
6. Review the information and select **Save and Deploy**.
108111

109112
</TabItem>
110113
<TabItem label="API" no-code="true">

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ import {
1414
GlossaryTooltip,
1515
APIRequest,
1616
Render,
17+
DashButton,
1718
} from "~/components";
1819

1920
[Magic Transit](/magic-transit/) customers using BYOIP can also benefit from the performance, reliability, and security that Cloudflare offers for HTTP-based applications. [Service bindings](/byoip/service-bindings/) allow BYOIP customers to selectively route traffic on a per-IP address basis to the CDN pipeline (which includes [Cache](/cache/), [Web Application Firewall (WAF)](/waf/), and more).
@@ -71,13 +72,15 @@ If you need to map only specific subdomains (and not all proxied DNS records) to
7172
<Tabs syncKey="dashPlusAPI">
7273
<TabItem label="Dashboard" no-code="true">
7374

74-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
75-
2. Go to **IP Addresses** > **Address Maps**.
76-
3. Select **Create an address map**.
77-
4. Choose the scope of the address map.
78-
5. Add the zones and IP addresses that you want to map.
79-
6. Name your address map.
80-
7. Review the information and select **Save and Deploy**.
75+
1. In the Cloudflare dashboard, go to the **Address Maps** page.
76+
77+
<DashButton url="/?to=/:account/ip-addresses/proxy-ips" />
78+
79+
2. Select **Create an address map**.
80+
3. Choose the scope of the address map.
81+
4. Add the zones and IP addresses that you want to map.
82+
5. Name your address map.
83+
6. Review the information and select **Save and Deploy**.
8184

8285
</TabItem>
8386
<TabItem label="API" no-code="true">

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/managed-rulesets.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ head:
99

1010
---
1111

12+
import { DashButton } from "~/components";
13+
1214
If you are interested in [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) but unsure of where to start, Cloudflare recommends using WAF Managed Rules. The Cloudflare security team creates and manages a variety of rules designed to detect common attack vectors and protect applications from vulnerabilities. These rules are offered in [managed rulesets](/waf/managed-rules/), like Cloudflare Managed and OWASP, which can be deployed with different settings and sensitivity levels.
1315

1416
***
@@ -43,18 +45,16 @@ After the association is complete, the JSON blob is added to the defined custom
4345

4446
## 2. Deploy Rulesets
4547

46-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and navigate to your account.
48+
1. In the Cloudflare dashboard, go to the **WAF** page.
4749

48-
2. Select Account Home > **WAF**.
50+
<DashButton url="/?to=/:account/application-security/waf" />
4951

5052
:::note
51-
52-
5353
**WAF** at the account level will only be visible on Enterprise plans. If you do not see this option, contact your account manager.
54-
55-
5654
:::
5755

56+
2. Select **Managed rulesets**.
57+
5858
3. Select **Deploy a managed ruleset**.
5959

6060
4. Under **Field**, Select *Hostname*. Set the operator as *equals*. The complete expression should look like this, plus any logic you would like to add:

0 commit comments

Comments
 (0)