Skip to content

Conversation

@micheledellipaoli-pagopa
Copy link
Contributor

No description provided.

@micheledellipaoli-pagopa micheledellipaoli-pagopa changed the title feat: add GRANT USAGE on catalog, attribute, tenant schemas and SELECT on tables to public_catalog_updater_user feat(public-catalog): add GRANT USAGE on catalog, attribute, tenant schemas and SELECT on tables to public_catalog_updater_user in prod Oct 28, 2025
V1.2__Grant_Select_to_PublicCatalogUpdater.sql: |-
GRANT USAGE ON SCHEMA "${NAMESPACE}_catalog" to "public_catalog_updater_user";
GRANT SELECT ON TABLE "${NAMESPACE}_catalog".eservice TO "public_catalog_updater_user";
Copy link
Contributor

@paolomanca-pagopa paolomanca-pagopa Oct 28, 2025

Choose a reason for hiding this comment

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

Sure about to give this granular permissions on specific tables?
A join with another table is enough to cause a permission error.

Otherwise you can set:
GRANT SELECT ON ALL TABLES IN SCHEMA "${NAMESPACE}_catalog".eservice TO "public_catalog_updater_user";

Same for other migration files

Copy link
Contributor

Choose a reason for hiding this comment

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

We opted to be as granular as possible with this user since it will copy data from the "private" catalog to the public catalog

@galales
Copy link
Contributor

galales commented Nov 27, 2025

replaced by #435

@galales galales closed this Nov 27, 2025
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.

4 participants