SubscriptionItem is different for Tableau Cloud/on-prem: currently only works for Cloud
評估
研究方向
Start at the subscription retrieval and update entry points used by server.subscriptions.get() and server.subscriptions.update(subscription), focusing on how SubscriptionItem.schedule_id is populated for Tableau Cloud. Reproduce the reported case with an active subscription and verify that schedule_id is returned and the update no longer fails with the null-schedule error.
由索引模型根據 Issue 內容生成。
描述
Describe the bug
When retrieving subscriptions using the TSC API on Tableau Online (Tableau Cloud), the SubscriptionItem.schedule_id field is always None, even for active subscriptions that were created with a valid schedule. This makes it impossible to update these subscriptions (e.g. suspend them), as the schedule ID is required for the update call.
Versions
Tableau: Tableau Online (Cloud)
Python: Python 3.11.10
TSC library: 0.38
To Reproduce
import tableauserverclient as TSC
tableau_auth = TSC.PersonalAccessTokenAuth(
token_name=TOKEN_NAME,
personal_access_token=TOKEN_SECRET,
site_id=SITE_ID
)
server = TSC.Server(SERVER_URL, use_server_version=True)
with server.auth.sign_in(tableau_auth):
all_subscriptions, pagination_item = server.subscriptions.get()
for subscription in all_subscriptions:
print(
f"Subscription ID: {subscription.id}, "
f"Name: {subscription.subject}, "
f"Suspended: {subscription.suspended}, "
f"Schedule ID: {subscription.schedule_id}, " # Always None
f"User ID: {subscription.user_id}"
)
Outputs:
Subscription ID: abc, Name: test test, suspended: False, Schedule ID: None, user ID: abc
Results
Even though the subscription is active and was created using a valid schedule, the subscription.schedule_id is always None. This causes server.subscriptions.update(subscription) to fail with the following error:
404023: Resource Not Found
Schedule 'null' could not be found.
- 主要語言
- Python
- 星號
- 716
- 分支
- 444
- 平均合併
- 1 天 2 小時
- 30 天內合併 PR
- 1
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
tableau/server-client-python 的其他 Issue
-
WorkbookItem.update() always sends an empty <dataAccelerationConfig/> even when never set可能已有人在做 @jacalata 於 14 天前認領。 未關閉in-progress
難度 2/5 1-3 小時 新手友好度 78/100
tableau/server-client-python#1884 ·
-
難度 2/5 1-3 小時 新手友好度 70/100
tableau/server-client-python#1865 ·
-
security: _validate_import_line_or_throw logs credential fields at DEBUG level可能已有人在做 @jacalata 於 54 天前認領。 未關閉in-progress
難度 2/5 1-3 小時 新手友好度 78/100
tableau/server-client-python#1829 · 1 則留言 ·
-
enhancement gap needs investigation stale
難度 2/5 1-3 小時 新手友好度 68/100
tableau/server-client-python#1322 · 2 則留言 ·
-
[Type2] Allow Incremental Refresh type schedules to be added via `server.schedules.add_to_schedule`未關閉help wanted Server-Side Enhancement ui-exists
難度 2/5 1-3 小時 新手友好度 68/100
tableau/server-client-python#1101 · 3 則留言 ·
查看 tableau/server-client-python 的全部 Issue
相似的 Issue
-
enhancement good first issue Stellar Wave trivial
難度 2/5 1-3 小時 新手友好度 75/100
StellarCanary/ProtocolCanary-Fixtures#258 ·
維護者通常 1 天內回覆
-
github_actions
難度 2/5 1-3 小時 新手友好度 65/100
Hochfrequenz/aibap.mcp#578 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 75/100
mishraprafful/multihull#150 ·
維護者通常 1 天內回覆
-
mp: /status reports the server class name as engine_type, not the configured engine可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
python-caldav/caldav#735 ·
維護者通常 1 天內回覆