Skip to content

Conversation

@sundarok
Copy link
Collaborator

@sundarok sundarok commented Oct 10, 2025

Summary by cubic

Fix first-time startup by removing hard-coded table owner/privilege statements in the Jira connections migration to avoid permission errors on fresh installs. Also added IDE files (*.idea) to .gitignore.

  • Bug Fixes
    • Removed ALTER OWNER and GRANT from migration 000015; table ownership now comes from the migration user set in config.yaml.

@sundarok sundarok linked an issue Oct 10, 2025 that may be closed by this pull request
Copy link
Contributor

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

Choose a reason for hiding this comment

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

No issues found across 2 files

@sundarok sundarok changed the title fix: Fixed first time startup issue Fix: Fixed first time startup issue Oct 10, 2025
@sundarok sundarok changed the title Fix: Fixed first time startup issue fix: fixed first time startup issue Oct 10, 2025
ALTER TABLE jira_connections OWNER TO app;
GRANT ALL PRIVILEGES ON TABLE jira_connections TO app;
-- Note: Table ownership and privileges are handled by the database connection user
-- The table will be owned by the user running the migration (configured in config.yaml)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please add this change as a new sql instead of changing existing one so as not to cause any migration issues

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.

First time startup issue

4 participants