topic Re: PAT needed but not allowed in "Advanced Data Engineering - 6.5L Deploy pipeline with the CL in Administration & Architecture

PAT needed but not allowed in "Advanced Data Engineering - 6.5L Deploy pipeline with the CLI Lab"

jonxu — Thu, 21 Nov 2024 02:53:08 GMT

It is stated in the lab notebook that:

Run the setup

Run the setup script for this lesson by running the cell below. This will ensure that:

The Databricks CLI is installed
Authentication is configured
A pipeline is created

However, when I tried to run the pipeline from web terminal, it says: "Error: cannot load Databricks config file: no configuration file found at /root/.databrickscfg; please create one first".

When I tried to install CLI and configure it, I will need personal token, which is disabled for our Databricks Academy user...

Please advise,

Jon

Re: PAT needed but not allowed in "Advanced Data Engineering - 6.5L Deploy pipeline with the CL

Walter_C — Thu, 21 Nov 2024 14:03:40 GMT

You can try by using the Oauth token for User to Machine, you can follow the steps in https://docs.databricks.com/en/dev-tools/cli/authentication.html#oauth-user-to-machine-u2m-authentication

Re: PAT needed but not allowed in "Advanced Data Engineering - 6.5L Deploy pipeline with the CL

jonxu — Thu, 21 Nov 2024 23:43:29 GMT

Thanks Walter for the quick response!

When I followed the instructions, I got error message when clicking on the link generated in step 2 as:

This dbc-c50de945-b335.cloud.databricks.com page can’t be found

No webpage was found for the web address: https://dbc-c50de945-b335.cloud.databricks.com/oidc/accounts/labuser8235016_1732229099@vocareum.com/v1/authorize?client_id=databricks-cli&code_challenge=5SGM_ZyVVFYhvxvGLbbWNYc9CKMl9zWnkyDV5CWIqWM&code_challenge_method=S256&redirect_uri=http%3A%2F%2Flocalhost%3A8020&response_type=code&scope=offline_access+all-apis&state=xlXxVzl1mUYWRHY01VOgmw

Re: PAT needed but not allowed in "Advanced Data Engineering - 6.5L Deploy pipeline with the CL

jonxu — Fri, 22 Nov 2024 00:02:47 GMT

... and if I start with step 5, using workspace-level authorisation, I ended up with "localhost refused to connect." in the generated link.