You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I have a workflow that utilizes the Databricks CLI to fetch the latest registered version of a model and updates a serving endpoint to that new model. This works in the dev workspace but fails in both staging and prod due to the same error (Invalid access to Org).
The commands used (databricks model-versions list, databricks serving-endpoints update-config) in the workflow works locally for all workspaces/environments but fails in GitHub Actions workflow on staging and prod.
Expected behavior
As the workflow works in the dev workspace I would expect it to work in staging and prod as well. Are there some authentication settings that might have to be tweaked to allow for GitHub Actions to use the REST API/CLI?
Description
I have a workflow that utilizes the Databricks CLI to fetch the latest registered version of a model and updates a serving endpoint to that new model. This works in the
dev
workspace but fails in bothstaging
andprod
due to the same error (Invalid access to Org).The commands used (
databricks model-versions list
,databricks serving-endpoints update-config
) in the workflow works locally for all workspaces/environments but fails in GitHub Actions workflow onstaging
andprod
.Expected behavior
As the workflow works in the
dev
workspace I would expect it to work instaging
andprod
as well. Are there some authentication settings that might have to be tweaked to allow for GitHub Actions to use the REST API/CLI?Debug Logs
Other Information
Occurs during GitHub Actions Workflow
The text was updated successfully, but these errors were encountered: