update README api keys section to reflect api endpoint change (https://github.com/gabledata/product/pull/811) #41
Conversation
|
I'm guessing we should wait to merge this until the release goes through? |
|
Also please check if there is anywhere in the product docs that needs to be updated. |
@geoffrey can you advise on waiting to merge documentation changes in relation to product releases? (release process is related but I'm not sure covers this) |
| - An API key that corresponds to the endpoint | ||
|
|
||
| You can find your API key by navigating to the `Settings -> API Keys` page of Gable. Under API Keys you can click `View` to reveal your API key. | ||
| You can find your API endpoint and key by navigating to the `Settings -> API Keys` page of Gable. Under API Keys you can click `View` to reveal your API key. |
There was a problem hiding this comment.
It sucks that we can't link directly to this because the domain differs per customer. We would have to have some way of noticing which deployment they're auth'd against (maybe this is accessible in cookies somehow?) and redirect to it.
We should wait on merging this until after the product release on Tuesday. I can take control of this PR and make sure it gets merged after the release if you want? Either way I'm going to set a personal reminder to make sure this gets merged next week. Additionally, I've added some notes to the Release Process Notion page. This is not a perfect process and should be discussed and revised at a later time. However, I don't think it's a priority. I'm going to page @adrianisk and @DevopsAdrian in Slack (as well as here) to add visibility. Lastly, |
In light of https://github.com/gabledata/product/pull/811, include the new change in the readme
here's the new change rendered:
