Paul Burridge

Results 6 comments of Paul Burridge

It is not necessary to use a separate file to tell the top level dependencies as below: `# via -r requirements.txt` - top level `# via -r requirements.txt, flask` -...

Also to update versions we simply delete those that are not top level from the file, remove any relevant fixed version then recompile.

I have always run without specifying an output file and before the change it did overwrite the existing file which suggests that is a valid workflow by design. (see below)...

Same issue here, worked then stopped working, how can I debug this further?

My workaround for a similar situation (in this case PAT with DATABRICKS_CLIENT_ID and DATABRICKS_CLIENT_SECRET envars set) ``` workspace_client = WorkspaceClient(token=token, auth_type="pat") config = workspace_client.config config.client_id = None config.client_secret = None...

I note the bundle deployment works fine after I set the values using the cli. `databricks apps update reporting-app --json '{"user_api_scopes": ["sql"], "description": "abc"}' --profile reporting` So workaround is comment...