[TYPE 3] Flow Run Notes
還沒有人認領這個 Issue。
評估
研究方向
Start at the flows/runs endpoint and inspect how flowRun XML is represented, including its backgroundJobId reference. Determine how available background-job notes should be exposed to non-admin creators without requiring a separate job query. Done means flow-run responses provide the requested notes when available and preserve the existing permissions context.
由索引模型根據 Issue 內容生成。
描述
Summary
Provide notes from the relevant background job in the flowRun XML.
Request Type
Type 3: new functionality
Requests for totally new functionality will generally be passed to the relevant dev team, but we probably can't give any useful estimate of how or when it might be implemented. If it is a feature that is 'about' the API or programmable access, here might be the best place to suggest it, but generally feature requests will be more visible in the Tableau Community Ideas forum and should go there instead.
Description
A clear and concise description of what the feature request is. If you think that the value of this feature might not be obvious, include information like how often it is needed, amount of work saved, etc. If your feature request is related to a file or server in a specific state, describe the starting state when the feature can be used, and the end state after using it. If it involves modifying files, an example file may be helpful.
If a non-admin creator is trying to get details about a flow run failure, it is currently not possible with the permissions context. flowRun XML contains a reference to a backgroundJobId, but if the creator is a non-admin, they are not able to query jobs, even by id, on a given site. If notes from the background job are available through the "flows/runs" endpoint, then a creator will not have to engage with a site/server admin to retrieve the details on the failure.
- 主要語言
- Python
- 星號
- 716
- 分支
- 445
- 平均合併
- 1 天 2 小時
- 30 天內合併 PR
- 1
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
tableau/server-client-python 的其他 Issue
-
in-progress
難度 2/5 1-3 小時 新手友好度 78/100
tableau/server-client-python#1884 ·
-
難度 2/5 1-3 小時 新手友好度 70/100
tableau/server-client-python#1865 ·
-
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
-
難度 1/5 1 小時以內 新手友好度 72/100
letsencrypt/cp-cps#353 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 84/100
PedestrianDynamics/pyFDS-Evac#394 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
DOI-USGS/pywatershed#421 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
python-pillow/Pillow#10087 · 1 則留言 ·
維護者通常 1 天內回覆