EMCP opened a new issue #16003:
URL: https://github.com/apache/superset/issues/16003


   ### Motivation
   
   I've been trying to get started with a basic empty apache superset.. and add 
a single data source (Postgresql).  So far I accidentally started wiring it via 
`superset -set-database-uri` which I later learned will change my apache 
supersets backend... not start examining my data.. no problem I start switching 
to the REST api.. but then I get stuck on the create database step because of 
CSRF 
   
   ### Proposed Change
   
   On the Swagger API docs (and perhaps the part around `superset 
-set-database-uri` make it cleaer what we're doing with databases.. even just a 
simple prompt in the `superset --help` telling me to go examine the REST api 
can clue me in .. in places where I should not be trying to use the CLI
   
   ### New or Changed Public Interfaces
   
   In the Swagger Docs I just need to know where or how to set the CSRF 
token... I am almost there but.. just not sure where FLASK is expecting to find 
the CSRF token.. so I just get constant 400 errors when trying to create my 
first DB
   
   ```
   Traceback (most recent call last):
     File "/scratch.py", line 96, in <module>
       response = create_db_connection(jwt_token=bearer_tokens['access_token'], 
db_ip=db_host, db_port=db_port, username=db_user, password=db_password, 
db_name=db_name)
     File "/scratch.py", line 43, in create_db_connection
       response.raise_for_status()
     File 
"/home/emcp/anaconda3/envs/stonks-consume-ibjts/lib/python3.9/site-packages/requests/models.py",
 line 943, in raise_for_status
       raise HTTPError(http_error_msg, response=self)
   requests.exceptions.HTTPError: 400 Client Error: BAD REQUEST for url: 
http://someip:8088/api/v1/database/
   ```
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to