Make it clearer that the redirect url needs to be updated

[b-per]

What are you changing in this pull request and why?

Right now, the docs are not really clear that the OAUTH_REDIRECT_URI parameter needs to be updated with the value gotten from before.

We list 'LOCATED_REDIRECT_URI' (which people need to update), like we list 'CONFIDENTIAL' which is a fixed string.

Checklist

• I have reviewed the Content style guide so my content adheres to these guidelines.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Sep 20, 2024 8:17am

[mirnawong1]

hey @b-per and @Lana-hl - thanks for working together on this! I'm going to tweak this to make it further clear bc you're totally right! and i also think that tags <> aren't always understood as 'replace'.

also, in the previous text we say: In the following example create or replace security integration query, replace YOUR_ACCESS_URL with the appropriate Access URL for your region and plan.'

but i don't see any reference to access URL?

CREATE OR REPLACE SECURITY INTEGRATION DBT_CLOUD
  TYPE = OAUTH
  ENABLED = TRUE
  OAUTH_CLIENT = CUSTOM
  OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
  OAUTH_REDIRECT_URI = 'LOCATED_REDIRECT_URI'
  OAUTH_ISSUE_REFRESH_TOKENS = TRUE
  OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;

[Lana-hl]

great point @mirnawong1 ! I do think it will make it clearer if we add back the [appropriate Access URL](https://docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses) for your region and plan part

[mirnawong1]

hey @b-per and @Lana-hl , how's this looking for you both: preview link. we could remove the comment in the code if it's tmi

[b-per]

I might recommend removing the comment because I don't know if the statement would work with it.

Nitpicking a bit, I think that LOCATED_REDIRECT_URI is an odd name to the parameter as well, but I don't really mind if we don't change it.

[mirnawong1]

ok i've updated it to this and added a screenshot that @Lana-hl provided:

[mirnawong1]

hey @b-per @Lana-hl , going to merge this pr now. let me know if you have any issues or other thoughts - will be happy to address in another pr! thank you again for the help!