acceptance/dashboards: use replace_ids.py and inline plan output in publish-failure-retry

- Replace fixed hex regex [[Repls]] with replace_ids.py called after the first
  deploy; the real dashboard ID is captured from state as [DASHBOARD1_ID].
- Inline the plan -o json | jq output directly into output.txt instead of
  saving to out.plan_published_change.json and trace cat-ing it.

Co-authored-by: Denis Bilenko

Author: denik

acceptance/bundle/resources/dashboards/publish-failure-retry/out.plan_published_change.json

@@ -4,7 +4,7 @@ Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/publish-failure-re
 Deploying resources...
 Error: cannot create resources.dashboards.dashboard1: Fault injected by test. (400 INJECTED)
 
-Endpoint: POST [DATABRICKS_URL]/api/2.0/lakeview/dashboards/[DASHBOARD_ID]/published
+Endpoint: POST [DATABRICKS_URL]/api/2.0/lakeview/dashboards/[DASHBOARD1_ID]/published
 HTTP Status: 400 Bad Request
 API error_code: INJECTED
 API message: Fault injected by test.
@@ -23,11 +23,9 @@ Resources:
   Dashboards:
     dashboard1:
       Name: my dashboard
-      URL:  [DATABRICKS_URL]/dashboardsv3/[DASHBOARD_ID]/published?[WSPARAM]=[NUMID]
+      URL:  [DATABRICKS_URL]/dashboardsv3/[DASHBOARD1_ID]/published?[WSPARAM]=[NUMID]
 
 >>> [CLI] bundle plan -o json
-
->>> cat out.plan_published_change.json
 {
   "action": "update",
   "old": false,
@@ -42,7 +40,7 @@ Updating deployment state...
 Deployment complete!
 {
   "method": "PATCH",
-  "path": "/api/2.0/lakeview/dashboards/[DASHBOARD_ID]",
+  "path": "/api/2.0/lakeview/dashboards/[DASHBOARD1_ID]",
   "body": {
     "display_name": "my dashboard",
     "parent_path": "/Workspace/Users/[USERNAME]/.bundle/publish-failure-retry/default/resources",
@@ -52,7 +50,7 @@ Deployment complete!
 }
 {
   "method": "POST",
-  "path": "/api/2.0/lakeview/dashboards/[DASHBOARD_ID]/published",
+  "path": "/api/2.0/lakeview/dashboards/[DASHBOARD1_ID]/published",
   "body": {
     "embed_credentials": false,
     "warehouse_id": "someid"

acceptance/bundle/resources/dashboards/publish-failure-retry/output.txt

@@ -17,13 +17,14 @@ fault.py "POST /api/2.0/lakeview/dashboards/*" 400 0 1
 # First deploy: dashboard is created and saved to state, but publish fails.
 errcode trace $CLI bundle deploy
 
+# Capture the dashboard ID from state so subsequent output is normalized.
+replace_ids.py
+
 # Dashboard should be in state (tracked) despite the publish failure.
 trace $CLI bundle summary
 
 # Plan should show published: false (saved state) -> true (desired).
-# Capture the Changes entry for 'published' to verify the diff direction.
-trace $CLI bundle plan -o json | jq '.plan["resources.dashboards.dashboard1"].changes.published' > out.plan_published_change.json
-trace cat out.plan_published_change.json
+trace $CLI bundle plan -o json | jq '.plan["resources.dashboards.dashboard1"].changes.published'
 
 # Discard first-deploy requests so the output only contains second-deploy
 # calls, making it easy to confirm no CREATE was issued.

acceptance/bundle/resources/dashboards/publish-failure-retry/script

@@ -7,10 +7,6 @@ RecordRequests = true
 [EnvMatrix]
 DATABRICKS_BUNDLE_ENGINE = ["direct"]
 
-[[Repls]]
-Old = "[0-9a-f]{32}"
-New = "[DASHBOARD_ID]"
-
 # Dashboard published URLs use ?o= (local testserver) or ?w= (cloud) for the workspace/org ID.
 [[Repls]]
 Old = '\?[ow]=\d+'