Skip to content

fix(cas): move CORS config under server.http#2858

Merged
migmartri merged 2 commits into
chainloop-dev:mainfrom
migmartri:fix-controlplane
Mar 15, 2026
Merged

fix(cas): move CORS config under server.http#2858
migmartri merged 2 commits into
chainloop-dev:mainfrom
migmartri:fix-controlplane

Conversation

@migmartri

@migmartri migmartri commented Mar 14, 2026

Copy link
Copy Markdown
Member

Summary

  • Move CORS configuration from server.cors to server.http.cors in the proto definition and Helm template so it is correctly loaded in production deployments

refs #2848

The CORS configuration was placed at the server level instead of under
server.http, causing it to not be loaded correctly in production.

Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 6 files

The CORS field was moved from Server to Server.HTTP in the proto,
which triggers buf's FIELD_NO_DELETE rule. Add an ignore_only
exception for this internal config proto.

Signed-off-by: Miguel Martinez <miguel@chainloop.dev>
Entire-Checkpoint: 657a990875a2

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="buf.yaml">

<violation number="1" location="buf.yaml:35">
P2: This file-wide `FIELD_NO_DELETE` ignore disables breaking-change checks for all future config-field deletions in `conf.proto`, not just the CORS move.

(Based on your team's feedback about cross-component and version compatibility.) [FEEDBACK_USED]</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Comment thread buf.yaml
- EXTENSION_NO_DELETE
- FIELD_SAME_DEFAULT
ignore_only:
FIELD_NO_DELETE:

@cubic-dev-ai cubic-dev-ai Bot Mar 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2: This file-wide FIELD_NO_DELETE ignore disables breaking-change checks for all future config-field deletions in conf.proto, not just the CORS move.

(Based on your team's feedback about cross-component and version compatibility.)

View Feedback

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At buf.yaml, line 35:

<comment>This file-wide `FIELD_NO_DELETE` ignore disables breaking-change checks for all future config-field deletions in `conf.proto`, not just the CORS move.

(Based on your team's feedback about cross-component and version compatibility.) </comment>

<file context>
@@ -31,6 +31,9 @@ modules:
         - EXTENSION_NO_DELETE
         - FIELD_SAME_DEFAULT
+      ignore_only:
+        FIELD_NO_DELETE:
+          - app/artifact-cas/internal/conf/conf.proto
   - path: app/controlplane/api
</file context>
Fix with Cubic

@migmartri migmartri merged commit 8409738 into chainloop-dev:main Mar 15, 2026
15 checks passed
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