Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .nextchanges/bundles/record-bind-history.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* Record deployment history for `bundle deployment bind` when deployment history is enabled. ([#7817](https://github.com/databricks/cli/pull/7817))
13 changes: 12 additions & 1 deletion acceptance/bin/nostamp.py
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,14 @@
is a 2-space indent, keys in input order, <>& left unescaped, and integers at full precision.
Tests under bundle/dms assert the stamp itself and must not use it.

Removed in three shapes plus the plan header:
Removed in these shapes:
1. deployment_id/version_id nested in a deployment block, recognized by the
neighbouring "kind" and "metadata_file_path", which are kept; version_id
== "" is kept (a Terraform state dump carries that for an unstamped job).
2. changes entries keyed "deployment.deployment_id" / "deployment.version_id".
3. a changes object emptied by (2), or already empty.
4. the recorded plan header field features.
5. deployment_id/latest_version_id in bundle.deployment; other settings are kept.
"""

import argparse
Expand All @@ -23,6 +24,7 @@
_STAMP_KEYS = ("deployment_id", "version_id")
_CHANGE_KEYS = ("deployment.deployment_id", "deployment.version_id")
_PLAN_HEADER_KEYS = ("features",)
_BUNDLE_STAMP_KEYS = ("deployment_id", "latest_version_id")


def scrub(node):
Expand Down Expand Up @@ -52,6 +54,15 @@ def render(data, indent):
if isinstance(data, dict):
for k in _PLAN_HEADER_KEYS:
data.pop(k, None) # 4. plan header, present only at the root
# 5. Strip the summary's DMS IDs, keeping deployment settings such as locks.
bundle = data.get("bundle")
if isinstance(bundle, dict):
deployment = bundle.get("deployment")
if isinstance(deployment, dict) and any(k in deployment for k in _BUNDLE_STAMP_KEYS):
for k in _BUNDLE_STAMP_KEYS:
deployment.pop(k, None)
if not deployment:
bundle.pop("deployment")
return json.dumps(data, indent=indent, ensure_ascii=False, separators=(",", ": "))


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ cleanupRemoveDashboard() {
trap cleanupRemoveDashboard EXIT

trace $CLI bundle deployment bind dashboard1 "${DASHBOARD_ID}" --auto-approve
trace print_state.py --no-dms > out.state_after_bind.json
trace print_state.py --no-dms | nostamp.py --indent 1 > out.state_after_bind.json
ETAG=$(jq '.state["resources.dashboards.dashboard1"].state.etag // .resources[0].instances[0].attributes.etag // "no-etag"' < out.state_after_bind.json)
echo $ETAG
add_repl $ETAG ETAG
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@

>>> [CLI] bundle deployment bind spec1 main.fspec_[UNIQUE_NAME].boundspec --auto-approve
Successfully bound feature_spec with an id 'main.fspec_[UNIQUE_NAME].boundspec'
Run 'bundle deploy' to deploy changes to your workspace
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@

>>> [CLI] bundle deployment bind spec1 main.fspec_[UNIQUE_NAME].boundspec --auto-approve
Warn: Failed to record deployment history for bind: failed to create deployment version: operations.resource_key must have a known resource type prefix (e.g. 'jobs.', 'pipelines.'): feature_specs.spec1

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'm taking a look whether we need to add feature_spec as a resource to DMS.

Successfully bound feature_spec with an id 'main.fspec_[UNIQUE_NAME].boundspec'
Run 'bundle deploy' to deploy changes to your workspace
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
Cloud = true
EnvMatrix.DMS = ["", "true"]
EnvMatrix.OUTPUT_MODE = ["plain", "recorded"]
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@

>>> [CLI] bundle deployment unbind spec1
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@

>>> [CLI] bundle deployment unbind spec1
6 changes: 0 additions & 6 deletions acceptance/bundle/deployment/bind/feature_spec/output.txt
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,6 @@
"name": "main.fspec_[UNIQUE_NAME].boundspec"
}

>>> [CLI] bundle deployment bind spec1 main.fspec_[UNIQUE_NAME].boundspec --auto-approve
Successfully bound feature_spec with an id 'main.fspec_[UNIQUE_NAME].boundspec'
Run 'bundle deploy' to deploy changes to your workspace

>>> [CLI] bundle summary
Name: test-bind-feature-spec-[UNIQUE_NAME]
Target: default
Expand All @@ -37,8 +33,6 @@ Resources:
>>> [CLI] bundle plan
Plan: 0 to add, 0 to change, 0 to delete, 1 unchanged

>>> [CLI] bundle deployment unbind spec1

>>> [CLI] bundle summary
Name: test-bind-feature-spec-[UNIQUE_NAME]
Target: default
Expand Down
4 changes: 2 additions & 2 deletions acceptance/bundle/deployment/bind/feature_spec/script
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ trace $CLI feature-engineering create-feature-spec --json "{
\"features\": [{\"feature_lookup\": {\"table\": \"$SCHEMA_FULL_NAME.user_features\", \"lookup_keys\": [\"user_id\"], \"feature_names\": [\"age\"]}}]
}" | jq '{name}'

trace $CLI bundle deployment bind spec1 $SCHEMA_FULL_NAME.boundspec --auto-approve
trace $CLI bundle deployment bind spec1 $SCHEMA_FULL_NAME.boundspec --auto-approve &> out.bind.$OUTPUT_MODE.txt
trace $CLI bundle summary

title "The bound feature spec matches the config, so there is nothing to change"
trace $CLI bundle plan

trace $CLI bundle deployment unbind spec1
trace $CLI bundle deployment unbind spec1 &> out.unbind.$OUTPUT_MODE.txt
trace $CLI bundle summary

trace $CLI feature-engineering delete-feature-spec $SCHEMA_FULL_NAME.boundspec
6 changes: 6 additions & 0 deletions acceptance/bundle/deployment/bind/feature_spec/test.toml
Original file line number Diff line number Diff line change
@@ -1,3 +1,9 @@
# Keep history warnings in separate outputs.
EnvMatrix.OUTPUT_MODE = ["plain", "recorded"]
EnvMatrixExclude.plain_history = ["DMS=true", "OUTPUT_MODE=plain"]
EnvMatrixExclude.recorded_without_history = ["DMS=", "OUTPUT_MODE=recorded"]
EnvVaryOutput = "OUTPUT_MODE"

Ignore = [
".databricks",
]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ rm -f "$OUT_REQUESTS"
trace $CLI bundle deployment bind foo $NEW_PIPELINE_ID --auto-approve &> out.bind-success.txt
trace print_requests.py '^//import-file/' '^//workspace/'

trace $CLI bundle summary -o json | jq .resources > out.summary.json
trace $CLI bundle summary -o json | jq .resources | nostamp.py > out.summary.json
trace $CLI bundle plan

trace musterr $CLI bundle deploy
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ rm -f "$OUT_REQUESTS"
trace $CLI bundle deployment bind foo $NEW_PIPELINE_ID --auto-approve &> out.bind-success.txt
print_requests.py '^//import-file/' '^//workspace/delete'

trace $CLI bundle summary -o json > out.summary.json
trace $CLI bundle summary -o json | nostamp.py > out.summary.json
trace $CLI bundle plan

rm -f "$OUT_REQUESTS"
Expand Down
8 changes: 8 additions & 0 deletions acceptance/bundle/dms/bind-immutable/databricks.yml.tmpl
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
bundle:
name: dms-bind-immutable-$UNIQUE_NAME
workspace:
sync_mode: immutable
resources:
jobs:
foo:
name: foo
2 changes: 2 additions & 0 deletions acceptance/bundle/dms/bind-immutable/out.test.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
Cloud = false
EnvMatrix.DMS = ["true"]
13 changes: 13 additions & 0 deletions acceptance/bundle/dms/bind-immutable/output.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@

>>> [CLI] bundle deployment bind foo [JOB_ID] --auto-approve
Successfully bound job with an id '[JOB_ID]'
Run 'bundle deploy' to deploy changes to your workspace

>>> MSYS_NO_PATHCONV=1 [CLI] bundle-deployments list-resources deployments/[DEPLOYMENT_ID] -o json
[
{
"last_action_type": "OPERATION_ACTION_TYPE_UPDATE",
"resource_id": "[JOB_ID]",
"resource_key": "jobs.foo"
}
]
8 changes: 8 additions & 0 deletions acceptance/bundle/dms/bind-immutable/script
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
envsubst < databricks.yml.tmpl > databricks.yml
job_id=$($CLI jobs create --json '{"name": "bind-target-'$UNIQUE_NAME'"}' | jq -r '.job_id')
add_repl "$job_id" JOB_ID

trace $CLI bundle deployment bind foo "$job_id" --auto-approve
deployment_id=$(MSYS_NO_PATHCONV=1 $CLI workspace get-status "/Workspace/Users/${CURRENT_USER_NAME}/.bundle/dms-bind-immutable-${UNIQUE_NAME}/default/state/resources.deployment.json" -o json | jq -r '.object_id')
trace MSYS_NO_PATHCONV=1 $CLI bundle-deployments list-resources "deployments/${deployment_id}" -o json | jq -S 'map({resource_key, resource_id, last_action_type})'
rm -f "$OUT_REQUESTS"
4 changes: 4 additions & 0 deletions acceptance/bundle/dms/bind-immutable/test.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# This test ensures that deployment history works with bind and immutable folders. This case is interesting
# because by default we record the snapshot path in deploy, but that is not available during bind. So it's important
# to ensure that we don't do that during deployment bind, and recording history continues to work.
Cloud = false
2 changes: 1 addition & 1 deletion acceptance/bundle/dms/bind-unbind/out.test.toml
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
Cloud = false
Cloud = true
EnvMatrix.DMS = ["true"]
66 changes: 63 additions & 3 deletions acceptance/bundle/dms/bind-unbind/output.txt
Original file line number Diff line number Diff line change
@@ -1,11 +1,56 @@

=== Bind an existing job with deployment history enabled

>>> musterr [CLI] bundle deployment bind foo [JOB_ID]
Plan: update resources.jobs.foo

Changes detected:
~ deployment: null -> {"kind":"BUNDLE","metadata_file_path":"/Workspace/Users/[USERNAME]/.bundle/dms-bind-unbind-[UNIQUE_NAME]/default/state/metadata.json"}
~ edit_mode: null -> "UI_LOCKED"
~ name: "bind-target-[UNIQUE_NAME]" -> "foo"

Error: this bind operation requires user confirmation, but the current console does not support prompting.
To proceed, use --auto-approve after reviewing the plan above.


>>> assert_not_exists.py .databricks/bundle/default/resources.json .databricks/bundle/default/resources.json.wal

>>> print_requests.py --dms //api/2.0/bundle

>>> [CLI] bundle deployment bind foo [JOB_ID] --auto-approve
Successfully bound job with an id '[JOB_ID]'
Run 'bundle deploy' to deploy changes to your workspace

=== Deploy keeps the bound job ID and enables shadow history
>>> jq {serial, features, resource_id: .state["resources.jobs.foo"].__id__} .databricks/bundle/default/resources.json
{
"serial": 2,
"features": {
"deployment_history_shadow": {}
},
"resource_id": "[JOB_ID]"
}

>>> print_requests.py --dms //versions --oneline
{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions", "q": {"version_id": "3"}, "body": {"cli_version": "[CLI_VERSION]", "operations": [{"action_type": "OPERATION_ACTION_TYPE_UPDATE", "resource_key": "jobs.foo"}], "version_type": "VERSION_TYPE_DEPLOY"}}
{"method": "PATCH", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/3/operations/jobs.foo", "q": {"update_mask": "state,error_message,resource_id,status"}, "body": {"error_message": "", "resource_id": "[JOB_ID]", "sequence_id": 0, "state": "{\"state\":{\"deployment\":{\"kind\":\"BUNDLE\",\"metadata_file_path\":\"/Workspace/Users/[USERNAME]/.bundle/dms-bind-unbind-[UNIQUE_NAME]/default/state/metadata.json\"},\"edit_mode\":\"UI_LOCKED\",\"format\":\"MULTI_TASK\",\"max_concurrent_runs\":1,\"name\":\"foo\",\"queue\":{\"enabled\":true}}}", "status": "OPERATION_STATUS_SUCCEEDED"}}
{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/3/complete", "body": {"completion_reason": "VERSION_COMPLETE_SUCCESS"}}

>>> [CLI] jobs get [JOB_ID]
{
"job_id": [JOB_ID],
"name": "bind-target-[UNIQUE_NAME]"
}

>>> MSYS_NO_PATHCONV=1 [CLI] bundle-deployments list-resources deployments/[DEPLOYMENT_ID] -o json
[
{
"last_action_type": "OPERATION_ACTION_TYPE_UPDATE",
"resource_id": "[JOB_ID]",
"resource_key": "jobs.foo"
}
]

=== Deploy keeps the bound job ID with recorded history

>>> [CLI] bundle deploy
Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/dms-bind-unbind-[UNIQUE_NAME]/default/files...
Expand Down Expand Up @@ -38,9 +83,9 @@ Resources: 0 created, 1 changed, 0 deleted, 0 unchanged
"job_id": [JOB_ID]
}

=== Rebind preserves the existing shadow history marker
=== Rebind preserves the existing shadow history marker without configuration

>>> [CLI] bundle deployment bind foo [JOB_ID] --auto-approve
>>> DATABRICKS_BUNDLE_DEPLOYMENT_HISTORY= [CLI] bundle deployment bind foo [JOB_ID] --auto-approve
Successfully bound job with an id '[JOB_ID]'
Run 'bundle deploy' to deploy changes to your workspace

Expand All @@ -52,6 +97,11 @@ Run 'bundle deploy' to deploy changes to your workspace
"resource_id": "[JOB_ID]"
}

>>> print_requests.py --dms //versions --oneline
{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions", "q": {"version_id": "7"}, "body": {"cli_version": "[CLI_VERSION]", "operations": [{"action_type": "OPERATION_ACTION_TYPE_UPDATE", "resource_key": "jobs.foo"}], "previous_version_id": "4", "version_type": "VERSION_TYPE_DEPLOY"}}
{"method": "PATCH", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/7/operations/jobs.foo", "q": {"update_mask": "state,error_message,resource_id,status"}, "body": {"error_message": "", "resource_id": "[JOB_ID]", "sequence_id": 0, "state": "{\"state\":{\"deployment\":{\"kind\":\"BUNDLE\",\"metadata_file_path\":\"/Workspace/Users/[USERNAME]/.bundle/dms-bind-unbind-[UNIQUE_NAME]/default/state/metadata.json\"},\"edit_mode\":\"UI_LOCKED\",\"format\":\"MULTI_TASK\",\"max_concurrent_runs\":1,\"name\":\"foo\",\"queue\":{\"enabled\":true}}}", "status": "OPERATION_STATUS_SUCCEEDED"}}
{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/7/complete", "body": {"completion_reason": "VERSION_COMPLETE_SUCCESS"}}

=== A subsequent deploy continues managing the same job

>>> [CLI] bundle deploy
Expand All @@ -66,3 +116,13 @@ Resources: 0 created, 0 changed, 0 deleted, 1 unchanged
},
"resource_id": "[JOB_ID]"
}

=== A rejected duplicate bind creates no history version

>>> musterr [CLI] bundle deployment bind foo [JOB_ID] --auto-approve
Error: Resource already managed

The bundle is already managing resource for resources.jobs.foo and it is bound to the requested ID [JOB_ID].


>>> print_requests.py --dms //versions
36 changes: 32 additions & 4 deletions acceptance/bundle/dms/bind-unbind/script
Original file line number Diff line number Diff line change
@@ -1,11 +1,29 @@
envsubst < databricks.yml.tmpl > databricks.yml

title "Bind an existing job with deployment history enabled"
job_id=$($CLI jobs create --json '{"name": "bind-target-'$UNIQUE_NAME'"}' | jq -r '.job_id')
# Match Jobs API defaults so the bind preview is identical locally and on cloud.
job_id=$($CLI jobs create --json '{"name": "bind-target-'$UNIQUE_NAME'", "format": "MULTI_TASK", "max_concurrent_runs": 1, "queue": {"enabled": true}}' | jq -r '.job_id')
add_repl "$job_id" JOB_ID
cleanup_bind_target() {
errcode $CLI bundle destroy --auto-approve >> LOG.cleanup 2>&1
errcode $CLI jobs delete "$job_id" >> LOG.cleanup 2>&1
}
trap cleanup_bind_target EXIT

trace musterr $CLI bundle deployment bind foo "$job_id"
# This bundle starts without state. A rejected bind must leave no committed state
# or pending WAL that a later command could recover.
trace assert_not_exists.py .databricks/bundle/default/resources.json .databricks/bundle/default/resources.json.wal
trace print_requests.py --dms //api/2.0/bundle
trace $CLI bundle deployment bind foo "$job_id" --auto-approve
trace jq '{serial, features, resource_id: .state["resources.jobs.foo"].__id__}' .databricks/bundle/default/resources.json
trace print_requests.py --dms //versions --oneline
trace $CLI jobs get "$job_id" | jq '{job_id, name: .settings.name}'
deployment_id=$(MSYS_NO_PATHCONV=1 $CLI workspace get-status "/Workspace/Users/${CURRENT_USER_NAME}/.bundle/dms-bind-unbind-${UNIQUE_NAME}/default/state/resources.deployment.json" -o json | jq -r '.object_id')
trace MSYS_NO_PATHCONV=1 $CLI bundle-deployments list-resources "deployments/${deployment_id}" -o json | jq -S 'map({resource_key, resource_id, last_action_type})'


title "Deploy keeps the bound job ID and enables shadow history"
title "Deploy keeps the bound job ID with recorded history"
trace $CLI bundle deploy
trace jq '{features, resource_id: .state["resources.jobs.foo"].__id__}' .databricks/bundle/default/resources.json

Expand All @@ -14,10 +32,20 @@ trace $CLI bundle deployment unbind foo
trace jq '{features, state}' .databricks/bundle/default/resources.json
trace $CLI jobs get "$job_id" | jq '{job_id}'

title "Rebind preserves the existing shadow history marker"
trace $CLI bundle deployment bind foo "$job_id" --auto-approve
rm -f "$OUT_REQUESTS"

title "Rebind preserves the existing shadow history marker without configuration"
trace DATABRICKS_BUNDLE_DEPLOYMENT_HISTORY= $CLI bundle deployment bind foo "$job_id" --auto-approve
trace jq '{features, resource_id: .state["resources.jobs.foo"].__id__}' .databricks/bundle/default/resources.json

trace print_requests.py --dms //versions --oneline

title "A subsequent deploy continues managing the same job"
trace $CLI bundle deploy
trace jq '{features, resource_id: .state["resources.jobs.foo"].__id__}' .databricks/bundle/default/resources.json

rm -f "$OUT_REQUESTS"

title "A rejected duplicate bind creates no history version"
trace musterr $CLI bundle deployment bind foo "$job_id" --auto-approve
trace print_requests.py --dms //versions
3 changes: 1 addition & 2 deletions acceptance/bundle/dms/bind-unbind/test.toml
Original file line number Diff line number Diff line change
@@ -1,3 +1,2 @@
RecordRequests = false
# Verify shadow history markers and resource IDs across bind, deploy, unbind, and rebind.
Cloud = false
Cloud = true
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
bundle:
name: dms-bind-upload-failure-$UNIQUE_NAME

resources:
jobs:
kept:
name: kept
upload_failed:
name: upload_failed
2 changes: 2 additions & 0 deletions acceptance/bundle/dms/bind-upload-failure/out.test.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
Cloud = false
EnvMatrix.DMS = ["true"]
24 changes: 24 additions & 0 deletions acceptance/bundle/dms/bind-upload-failure/output.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@

=== A remote state upload failure fails the bind version

>>> fault.py POST /api/2.0/workspace-files/import-file/**resources.json 400 0 1

>>> musterr [CLI] bundle deployment bind upload_failed [JOB_ID] --auto-approve
Error: Fault injected by test. (400 INJECTED)

Endpoint: POST [DATABRICKS_URL]/api/2.0/workspace-files/import-file/Workspace%2FUsers%2F[USERNAME]%2F.bundle%2Fdms-bind-upload-failure-[UNIQUE_NAME]%2Fdefault%2Fstate%2Fresources.json?overwrite=true
HTTP Status: 400 Bad Request
API error_code: INJECTED
API message: Fault injected by test.


>>> print_requests.py --dms //complete --oneline
{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/5/complete", "body": {"completion_reason": "VERSION_COMPLETE_FAILURE"}}

=== Remote state still contains only the successful bindings

>>> [CLI] bundle summary -o json
{
"kept": "[JOB_ID]",
"upload_failed": null
}
15 changes: 15 additions & 0 deletions acceptance/bundle/dms/bind-upload-failure/script
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
envsubst < databricks.yml.tmpl > databricks.yml
job_id=$($CLI jobs create --json '{"name": "bind-target-'$UNIQUE_NAME'"}' | jq -r '.job_id')
add_repl "$job_id" JOB_ID
$CLI bundle deployment bind kept "$job_id" --auto-approve &> LOG.setup
rm -f "$OUT_REQUESTS"

title "A remote state upload failure fails the bind version"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Because of API failing, the remote deployment state is not updated. In this case, deployment history does capture the bind operation but marks it as a failed version.

trace fault.py "POST /api/2.0/workspace-files/import-file/**resources.json" 400 0 1
trace musterr $CLI bundle deployment bind upload_failed "$job_id" --auto-approve
trace print_requests.py --dms //complete --oneline

rm -rf .databricks
title "Remote state still contains only the successful bindings"
trace $CLI bundle summary -o json | jq '.resources.jobs | map_values(.id // null)'
rm -f "$OUT_REQUESTS"
1 change: 1 addition & 0 deletions acceptance/bundle/dms/bind-upload-failure/test.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Cloud = false # Inject a remote state-upload failure.
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,4 @@ Warn: Could not enable deployment history for this deploy: failed to create depl
Warn: Could not enable deployment history for this deploy: failed to create deployment version: operations.resource_key must have a known resource type
Warn: Failed to complete deployment history version: Internal error
Error: cannot create resources.secrets.foo: response body: stream error: stream ID 73; INTERNAL_ERROR; received from peer
Warn: Failed to record deployment history for bind: operations.resource_key must have a known resource type
Loading
Loading