Skip to content

fix incorrect controller redirects#676

Draft
boddumanohar wants to merge 27 commits intomainfrom
issue-218
Draft

fix incorrect controller redirects#676
boddumanohar wants to merge 27 commits intomainfrom
issue-218

Conversation

@boddumanohar
Copy link
Copy Markdown
Member

fixes: simplyblock/vela#218
When the controller generates redirects, they lack the path prefix that the controller runs under,. Instead of /vela/foo the it will redirect to /foo. This happens for example to account for presence/lack of trailing slashes.

name: vela-controller-config
data:
VELA_ROOT_PATH: {{ .Values.controller.env.VELA_ROOT_PATH | quote }}
UVICORN_ROOT_PATH: {{ .Values.controller.env.VELA_ROOT_PATH | quote }}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this will resolve the issue, it basically duplicates what the variable above already does. FastAPI is already aware it's running with a root path, it's just the URL generation that's failing.

See this discussion on the handling: fastapi/fastapi#14038 (reply in thread). It's been a while since I thought about this, but iirc the fix was to adapt the url_path_for helper to use request.url_for(...).path instead of app.url_path_for. But this needs confirmation.

Base automatically changed from dev to main March 19, 2026 14:34
@boddumanohar boddumanohar changed the base branch from main to dev March 20, 2026 05:59
boddumanohar and others added 23 commits March 20, 2026 16:27
This is required to check on branch creation/modification within which
bounds the operation may be conducted.
The recent changes on the resource limit implementation exposed an issue
with the implementation of system limits. They shouldnt't be a third,
global scope of resources, but rather a default for organization limits
on creation. This change addresses this, by introducing a separate,
appropriately named table for handling these defaults. The system-level
endpoints are removed as they are not needed anymore, and a migration
ensures existing system limits are converted to the correct values.
The workflow simply referenced the built image tage, adding the digest
ensures helm detects changes and redeploys when a new image is built.
The previous version failed to reuse the existing enum datatype. The
change makes sure it is referenced instead.
Base automatically changed from dev to main March 25, 2026 12:30
mxsrc added 2 commits March 25, 2026 18:18
When using double quotations, values that contain bash instructions will
attempt to be resolved, for example credentials using '$' symbols might
be invalidated this way. This switches to single quotes for all inputs
that are used directly, avoiding this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants