bug:API Response of the scripts and variables it's different from the documentation
@rubenfiszel is already working on this.
Since Mar 6, 2025.
Assessment
This issue has not been assessed yet.
Description
Describe the bug
I'm using the APIs to list users and scripts on POstman and I'm getting a response differente that shows on the documentation.in my responses , I've missing fields such as created_by, folders,groups.Am I the only one with this problem?
To reproduce
Use GET
/w/{workspace}/scripts/list
Pass the Bearer Token
Pass the workspace
Send Request
See Response 200
Use GET
/w/{workspace}/users/list
Pass the Bearer Token
Pass the workspace
Send Request
See Response 200
Expected behavior
[
{
"email": "…",
"username": "…",
"is_admin": true,
"is_super_admin": true,
"created_at": "2025-03-06T13:46:50.225Z",
"operator": true,
"disabled": true,
"groups": [
"…"
],
"folders": [
"…"
],
"folders_owners": [
"…"
]
}
]
[
{
"workspace_id": "…",
"hash": "…",
"path": "…",
"parent_hashes": [
"…"
],
"summary": "…",
"description": "…",
"content": "…",
"created_by": "…",
"created_at": "2025-03-06T13:46:50.225Z",
"archived": true,
"schema": {},
"deleted": true,
"is_template": true,
"extra_perms": {
"ANY_ADDITIONAL_PROPERTY": true
},
"lock": "…",
"lock_error_logs": "…",
"language": "python3",
"kind": "script",
"starred": true,
"tag": "…",
"has_draft": true,
"draft_only": true,
"envs": [
"…"
],
"concurrent_limit": 1,
"concurrency_time_window_s": 1,
"concurrency_key": "…",
"cache_ttl": 1,
"dedicated_worker": true,
"ws_error_handler_muted": true,
"priority": 1,
"restart_unless_cancelled": true,
"timeout": 1,
"delete_after_use": true,
"visible_to_runner_only": true,
"no_main_func": true,
"codebase": "…",
"has_preprocessor": true
}
]
Screenshots
Browser information
https://app.windmill.dev/openapi.html#tag/script/GET/w/{workspace}/scripts/list
Application version
No response
Additional Context
No response
- Dominant language
- Rust
- Stars
- 18k
- Forks
- 1.1k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 328
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from windmill-labs/windmill
-
webmux_oneshot
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
windmill-labs/windmill#10877 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
windmill-labs/windmill#11234 ·
-
bug webmux_oneshot
windmill-labs/windmill#11219 · 1 assignee ·
-
bug
windmill-labs/windmill#11196 · 1 assignee ·
-
windmill-labs/windmill#11002 · 1 assignee ·
All issues in windmill-labs/windmill
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100