Passing custom gunicorn config for flask extension
Metadata
Current evaluation
Requests customizable Gunicorn settings for flask-framework, especially async workers; current docs claim sync/async support, but this unlabelled issue has no recorded triage or linked resolution.
Suggested action: needs triage
Reason: The report has no labels, assignee, comments, or maintainer assessment, so it still meets the needs_triage criteria. Current documentation says the Flask extension supports synchronous and asynchronous workers, while version-specific Gunicorn configuration remains in the source, so a maintainer should verify whether existing behavior fully resolves the request before closing it.
Evaluated by: mr-cal-bot
Impact:
48
Quick Win:
18
Complexity:
46
Confidence:
86
Actionability:
70
Issue body
### What needs to get done
Currently, the gunicorn config is hardcoded [here](https://github.com/canonical/rockcraft/blob/main/extensions/flask-framework/gunicorn.conf.py). However, in many scenarios, it is essential to override some of the settings (Example: changing worker type to async workers, modifying number of workers, etc).
This can be done either with a file override, passing the `GUNICORN_CMD_ARGS` env variable, or allowing CLI arguments.
See [the docs](https://docs.gunicorn.org/en/stable/settings.html) for more info
In my case, we need to use `async` workers instead of the default `sync` ones
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
18
Complexity:
46
Confidence:
86
Actionability:
70
|
needs triage | Requests customizable Gunicorn settings for flask-framework, especially async workers; current docs claim sync/async support, but this unlabelled issue has no recorded triage or linked resolution. | |
| qwen/qwen3.6-35b-a3b |
Impact:
35
Quick Win:
14
Complexity:
45
Confidence:
70
Actionability:
75
|
keep open | Feature request to allow overriding the hardcoded gunicorn config in flask-framework extension. No implementation yet after 712 days. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
10
|
close stale | Request to allow custom gunicorn config overrides (worker type, worker count, etc.) in the flask-framework extension. The specific async-worker use case has since been implemented via PR #747 (gevent detection), but the broader arbitrary-config request remains unaddressed. Issue is 693 days old with zero comments, no labels, and no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
40
Confidence:
80
Support Request:
10
|
close stale | Feature request to allow overriding the hardcoded Gunicorn configuration in the Flask extension via env vars, CLI args, or config files. Currently untriaged and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | Feature request to allow overriding the hardcoded gunicorn configuration in the flask-framework extension via env vars, CLI args, or config files. Currently unlabelled and inactive for over 1.5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
25
Confidence:
75
Support Request:
5
|
needs triage | Feature request to allow overriding the hardcoded Gunicorn configuration in the Flask extension via env vars, CLI args, or config files. Currently untriaged with no maintainer response in over 1.7 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #747 Feat(extension): Enable Async Gunicorn workers for Flask and Django e… | rockcraft | merged | Merged PR #747 via commit ba8c0d79, adding automatic async Gunicorn workers for Flask and Django extensions when gevent is present, with an explicit synchronous override. |