Created API key empty just after uploading a table
See original GitHub issueContext
This bug has been found using CARTOframes. When a map that uses a private table is published a Maps API key is created.
Steps to Reproduce
Using CARTOframes:
- Upload a table to CARTO:
to_carto(gdf, 'new_table_name', if_exists='replace')
- Create a Map:
map_viz = Map(Layer('new_table_name'))
- Publish the Map:
map_viz.publish(name='New_Table_Name', password='1234', if_exists='replace')
Current Result
If the table has been just uploaded the API key is not properly created (empty tables) and there is no Exception from the backend.
Expected result
API key creation should work or at least raise an Exception.
Additional info
Related to:
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (15 by maintainers)
Top Results From Across the Web
How do I reset my API Key? - Telesign Support
1. Once you've navigated to the API Keys page in My TeleSign, click on blue dots in the far right field of the...
Read more >Troubleshooting API Key Validation Issues - Gravity Forms
In this article, we will help you troubleshoot issues with validating an API key for an add-on service.
Read more >Create API key API | Elasticsearch Guide [8.5] | Elastic
The API keys are created by the Elasticsearch API key service, ... When it is not specified or is an empty array, then...
Read more >API - Common Troubleshooting - Airtable Support
The API key or access token was passed correctly in the request, but you do not have permission to perform the action in...
Read more >How to Get a YouTube API Key [Tutorial + Examples]
3. On the new project dashboard, click Explore & Enable APIs. After creating a project, you'll be taken to a brand new dashboard...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After talking to @cmongut we’ll go with option 3, although it’s not super-prioritary 😛
I cannot reproduce the issue, thus I don’t know what happened, but I’ve checked one of the wrong API keys are correct in our metadata database and the pg_role was created, but it hadn’t any GRANT.
I’m going to force that very same error introducing an exception in the moment the permissions are granted, and do an E2E test locally to see what happens.