remove tabs in prep for migration

Author: aimurphy

modules/ROOT/partials/functions-ui-common-steps-pt1.adoc

@@ -0,0 +1,7 @@
+. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+
+. Click the name of the tenant where you want to deploy a function.
+
+. On the *Functions* tab, click *Create Function*.
+
+. Enter a function name.

modules/ROOT/partials/functions-ui-common-steps-pt2.adoc

@@ -0,0 +1,37 @@
+. Select the namespace and one or more input topics for the function.
+
+. If needed, select an output namespace and topics.
++
+Whether you need to specify an output topic depends on the function's logic.
+For example, the `cast` xref:developing:astream-functions-transform.adoc[transform function] needs an output topic to receive the transformed messages.
+
+. Optional: Select a log topic.
++
+The log topic is a separate output topic for messages containing additional `loglevel`, `fqn`, and `instance` properties.
+
+. Optional: Configure advanced settings:
++
+* *Instances*: Enter a number of sink instances to run.
+* *Processing Guarantee*: Select one of the following:
+** *ATLEAST_ONCE* (default): Each message sent to the function can be processed one or more times.
+** *ATMOST_ONCE*: Each message sent to the function is processed 0 or 1 times.
+This means there is a change that a message is not processed.
+** *EFFECTIVELY_ONCE*: Each message sent to the function has only one output associated with it.
+* *Timeout*: Set a timeout limit.
+* *Auto Acknowledge*: Enable or disable automatic message acknowledgment.
+
+. If needed, provide a JSON-formatted config key for your function.
+This configuration depends on your function code.
+
+. Click *Create*.
+
+. Confirm your function was created on the *Functions* tab.
++
+You can also verify the function deployment with the {pulsar-short} CLI:
++
+[source,shell]
+----
+./bin/pulsar-admin functions list --tenant $TENANT
+----
+
+Once created, the function starts processing messages from the input topics according to its logic.

modules/apis/pages/index.adoc

@@ -400,33 +400,26 @@ eyJhbGciOiJSUzI1NiIsI...
 Create a new {pulsar-short} token (JWT) for a given tenant and cluster.
 You can get the cluster name from <<get-tenant-details>>.
 
-[tabs]
-======
 v2 endpoint::
-+
---
 The `v2/streaming/tenants/$TENANT/tokens` endpoint returns a raw string JWT with an unlimited lifetime:
-
++
 [source,curl]
 ----
 curl -sS --fail -L -X POST "https://api.astra.datastax.com/v2/streaming/tenants/$TENANT/tokens" \
 --header "Authorization: Bearer $ASTRA_TOKEN" \
 --header "X-DataStax-Pulsar-Cluster: $CLUSTER"
 ----
-
++
 .Result
 [source,json]
 ----
 Output: new raw string JWT
 eyJhbGciOiJSUzI1NiIsI...
 ----
---
 
 v3 endpoint::
-+
---
 The `v3/streaming/tenants/$TENANT/tokens` endpoint returns a JSON response and accepts additional token parameters:
-
++
 [source,curl,subs="+quotes"]
 ----
 curl -sS --fail -L -X POST "https://api.astra.datastax.com/v3/streaming/tenants/$TENANT/tokens" \
@@ -438,13 +431,13 @@ curl -sS --fail -L -X POST "https://api.astra.datastax.com/v3/streaming/tenants/
   "type": "**TYPE**"
 }'
 ----
-
++
 Replace the following:
-
++
 * **`EXPIRATION`**: The token lifetime expressed as a number and unit, such as `1d` for one day.
 * **`ROLE`**: A string describing the token's role.
 * **`TYPE`**: The token's privilege level, either `admin` or `non-admin`.
-
++
 .Result
 [source,json]
 ----
@@ -454,8 +447,6 @@ Replace the following:
   "token": "eyJhbGciOiJSUzI1NiIsI..."
 }
 ----
---
-======
 
 === Delete a {pulsar-short} token
 

modules/developing/pages/astream-cdc.adoc

@@ -269,11 +269,7 @@ After you <<create-tenant,create a tenant>> and <<create-table,create tables>>,
 
 For <<multi-region-cdc,multi-region databases>>, you must use the xref:astra-db-serverless:api-reference:devops-api.adoc[{product-short} {devops-api}] to enable CDC in secondary regions.
 
-[tabs]
-======
-{astra-ui}::
-+
---
+==== Enable CDC in the {astra-ui}::
 . In the {astra-ui}, click the name of the database where you want to enable CDC.
 +
 If you created the demo table in <<create-table>>, select the database where you created that table.
@@ -291,11 +287,9 @@ If you created the demo table in <<create-table>>, select the database where you
 Enabling CDC on any table disables the *Add a region* functionality in the {astra-ui} for that database.
 You must use the {product-short} {devops-api} to add a region after enabling CDC.
 ====
---
 
-{product-short} {devops-api}::
-+
---
+==== Enable CDC with the {product-short} {devops-api}
+
 [IMPORTANT]
 ====
 CDC for multi-region {astra-db} {db-serverless-vector} databases is available only to qualified participants in this private preview release.
@@ -307,10 +301,9 @@ If you're interested in this private preview feature, contact your {company} acc
 
 Use the {product-short} {devops-api} to enable CDC on one or more tables in the same database in the same request.
 
-You can use these endpoints to enable CDC in single-region and multi-region databases.
+You can use the following endpoints to enable CDC in single-region and multi-region databases.
+To check the CDC configuration for a database or table, see <<get-cdc>>.
 
-[tabs]
-====
 Enable CDC after deploying a region::
 +
 Use these steps to enable CDC in a single-region database or in previously-deployed regions of a multi-region database.
@@ -431,11 +424,8 @@ The tenant must be in the same region as specified in `region`.
 +
 All tables replicated to the new region automatically have CDC enabled.
 The `astracdc` namespace and CDC topics for each table are created in the specified regional tenant.
-====
 
-To check the CDC configuration for a database or table, see <<get-cdc>>.
---
-======
+==== CDC topics
 
 When you enable CDC on a database for the first time, {astra-db} automatically creates an `astracdc` namespace in your streaming tenant.
 For each table where you enable CDC, {astra-db} creates two topics in the `astracdc` namespace:
@@ -789,23 +779,16 @@ However, be aware of the following limitations:
 
 You can check your active CDC configurations in the {astra-ui} or with the {product-short} {devops-api}.
 
-[tabs]
-======
-{astra-ui}::
-+
---
+=== Check CDC status in the {astra-ui}
+
 . In the {astra-ui}, click the name of the database that you want to inspect.
 
 . Click the *CDC* tab, and then review the list of tables where you have enabled CDC.
 
 . Click a table's name to inspect the table's CDC configuration.
---
 
-{product-short} {devops-api}::
-+
---
-[tabs]
-====
+=== Check CDC status with the {product-short} {devops-api}
+
 By database::
 +
 Use `{devops-api-ref-url}#tag/Database-Operations/operation/getCDC[GET /v3/databases/**DB_ID**/cdc]` to get CDC configuration details for an entire database:
@@ -889,9 +872,6 @@ For multi-region databases with CDC enabled in multiple regions, the `regions` a
   }
 ]
 ----
-====
---
-======
 
 [#put-cdc]
 === Update a database's CDC configuration
@@ -1036,23 +1016,30 @@ CDC is automatically disabled if you drop a table, terminate a database, or remo
 You can remove a table's CDC configuration without deleting the table.
 For multi-region databases, this disables CDC for the table across all regions.
 
-[tabs]
-======
-{astra-ui}::
+Disabling CDC doesn't remove the associated namespace, topics, or {astra-stream} tenant:
+
+* If you reenable CDC for the same table, the existing topics are reused with the existing records.
+
+* If you want to discard a table's CDC records, you must manually remove the associated {astra-stream} artifacts after disabling CDC:
 +
---
+** If you remove CDC from a table, then you can delete the table's `data-` and `log-` topics from the `astracdc` namespace in the {astra-stream} tenant.
+For multi-region databases, make sure that you delete the topics in the tenant for each region where the database is deployed
+** If you remove CDC from all tables in a region, and you no longer need CDC in that region, then you can delete the `astracdc` namespace from the {astra-stream} tenant in that region.
+Deleting the namespace also deletes the topics within that namespace.
+** If you remove CDC from all of a database's tables, and you no longer need an {astra-stream} tenant for any reason, you can delete the entire tenant.
+
+==== Disable CDC with the {astra-ui}
+
 . In the {astra-ui}, click the name of the database where you want to disable CDC.
 
 . Click the *CDC* tab.
 
 . In the *Change Data Capture* list, click the table's name.
 
 . Click *Disable* to remove the table's CDC configuration.
---
 
-{product-short} {devops-api}::
-+
---
+==== Disable CDC with the {product-short} {devops-api}::
+
 Use `{devops-api-ref-url}#tag/Database-Operations/operation/deleteCDC[DELETE /v3/databases/**DB_ID**/cdc]` to disable CDC for a table:
 
 [source,curl,subs="+quotes"]
@@ -1083,20 +1070,6 @@ If you want to disable CDC for multiple tables at once, include an object for ea
 You can use `PUT /v3/databases/**DB_ID**/cdc` to make multiple changes to a database's CDC configuration in one request, including additions, changes, and removals of tables and regions.
 For more information, see <<put-cdc>>.
 ====
---
-======
-
-Disabling CDC doesn't remove the associated namespace, topics, or {astra-stream} tenant:
-
-* If you reenable CDC for the same table, the existing topics are reused with the existing records.
-
-* If you want to discard a table's CDC records, you must manually remove the associated {astra-stream} artifacts after disabling CDC:
-+
-** If you remove CDC from a table, then you can delete the table's `data-` and `log-` topics from the `astracdc` namespace in the {astra-stream} tenant.
-For multi-region databases, make sure that you delete the topics in the tenant for each region where the database is deployed
-** If you remove CDC from all tables in a region, and you no longer need CDC in that region, then you can delete the `astracdc` namespace from the {astra-stream} tenant in that region.
-Deleting the namespace also deletes the topics within that namespace.
-** If you remove CDC from all of a database's tables, and you no longer need an {astra-stream} tenant for any reason, you can delete the entire tenant.
 
 == See also