fix: add missing http_trigger_version_seq grants

[HugoCasa]

Important

Add migration scripts to grant permissions on http_trigger_version_seq to windmill_user and windmill_admin.

• Migrations:
  • Adds 20250526173025_http_trigger_seq_grants.up.sql to grant all permissions on http_trigger_version_seq to windmill_user and windmill_admin.
  • Adds 20250526173025_http_trigger_seq_grants.down.sql as a placeholder for down migration.

^{This description was created by for 94b03ed. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 94b03ed in 1 minute and 19 seconds. Click for details.

• Reviewed 17 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. backend/migrations/20250526173025_http_trigger_seq_grants.down.sql:1

• Draft comment:
  Down migration is incomplete. Add SQL commands to revoke privileges (e.g., REVOKE ALL ON SEQUENCE ...) to reverse the changes.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% The file is clearly a placeholder with just a comment. However, without seeing the corresponding up migration file, I cannot verify if there are actually any privileges being granted that need to be revoked. The comment makes assumptions about what the up migration does. I don't have access to the up migration file to confirm if there are actually any sequence privileges being granted that need to be revoked. While the comment might be correct, keeping it would violate the rule that we need STRONG EVIDENCE that the comment is correct. Without seeing the up migration, we can't be certain. Delete the comment since we lack the context to verify its correctness, and speculative comments should be avoided.

2. backend/migrations/20250526173025_http_trigger_seq_grants.up.sql:1

• Draft comment:
  Placeholder comment in up migration; update or remove comment to reflect actual changes.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. backend/migrations/20250526173025_http_trigger_seq_grants.up.sql:2

• Draft comment:
  Using 'GRANT ALL' may be overly permissive. Consider granting only the necessary privileges for security best practices.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. backend/migrations/20250526173025_http_trigger_seq_grants.up.sql:3

• Draft comment:
  Missing newline at end-of-file. Consider adding a newline for consistency and best practices.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_MaOpoXxqzq3JCRnv

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}