server_address doesn't get updated on workbook publish
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 58/100
Rechercherichtung
Start at workbooks.publish and compare the connections= path with the deprecated connection_credentials= path. Inspect tableauserverclient/models/connection_credentials.py and server/request_factory.py around line 38, then reproduce publishing with differing dev.example.com and production.example.com addresses. Done means the embedded connection's server_address is updated during publish and the workbook connects successfully.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
I'm working on a script that would push one workbook to multiple Tableau sites. Each site has a different database to connect to, so the embedded connection needs to be updated appropriately.
I'm trying to accomplish this by updating the embedded datasource connection information in the packaged workbook. Feel free to let me know if there's a better way to do this as I'm new to Tableau in general.
Currently, I have this:
conn_creds = TSC.ConnectionCredentials(name=rds_user,
password=rds_pass)
# Create a connection and add the above credentials to it
connection = TSC.ConnectionItem()
connection.server_address = rds_host
connection.server_port = rds_port
connection.connection_credentials = conn_creds
# Publish the workbook to tableau
publish_item = server.workbooks.publish(new_workbook,
workbook_file,
publish_mode,
connections=[connection])
This seems to work if the workbook was exported with the server_address set to the same thing as my rds_host above. So if rds_host and the server address in the workbook are both dev.example.com, it will update the credentials and publish correctly.
However, if rds_host is production.example.com and the workbook has dev.example.com, Tableau returns a failed to establish a connection to your datasource error message even though the credentials are correct.
Before I tried the above solution, I was using the (now deprecated?) connection_credentials attribute like this:
conn_creds = TSC.ConnectionCredentials(name=rds_user,
password=rds_pass)
# Publish the workbook to tableau
publish_item = server.workbooks.publish(new_workbook,
workbook_file,
publish_mode,
connection_credentials=conn_creds)
This had the same effect of updating the username/password correctly, but would not update the server_address.
https://tableau.github.io/server-client-python/docs/api-ref#workbooks under workbooks.publish actually does not mention the connections= attribute at all, only connection_credentials. There was a warning message logged saying it was deprecated that lead me to use connections.
https://tableau.github.io/server-client-python/docs/api-ref#connections under ConnectionCredentials class mentions server_address and server_port attributes, but they don't seem to exist in https://github.com/tableau/server-client-python/blob/v0.7/tableauserverclient/models/connection_credentials.py and aren't used in https://github.com/tableau/server-client-python/blob/v0.7/tableauserverclient/server/request_factory.py#L38
Please let me know if I need to clarify anything or if more information is needed. I haven't looked at the code too much for this library yet, but when I get some time I planned on testing the same process with the rest api directly to verify that it isn't an issue with the server api itself.
- Vorherrschende Sprache
- Python
- Sterne
- 716
- Forks
- 446
- Ø Merge
- 8 T. 8 Std.
- Gemergte PRs (30 T.)
- 2
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus tableau/server-client-python
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
tableau/server-client-python#1865 ·
-
in-progress
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
tableau/server-client-python#1829 · 1 Kommentar ·
-
enhancement gap needs investigation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
tableau/server-client-python#1322 · 1 Kommentar ·
-
[Type2] Allow Incremental Refresh type schedules to be added via `server.schedules.add_to_schedule` Offenhelp wanted Server-Side Enhancement ui-exists
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
tableau/server-client-python#1101 · 3 Kommentare ·
-
enhancement good first issue
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
tableau/server-client-python#783 · 5 Kommentare ·
Alle Issues in tableau/server-client-python
Ähnliche Issues
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 90/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
zostera/django-bootstrap4#894 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
use-agent-os/agent-os#3276 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
NousResearch/hermes-agent#117848 ·