We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this a request for help?: No
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report
Version of Helm and Kubernetes: N/A
Which chart: jfrog/jfrog-platform
jfrog/jfrog-platform
Which product license (Enterprise/Pro/oss): N/A
JFrog support reference (if already raised with support team): N/A
What happened:
The example here:
https://github.com/jfrog/charts/blob/master/examples/jfrog-platform/docs/external-postgres.md
— is insufficient for PostgreSQL 15+, because it assumes that the public schema is globally writable, which isn't true for 15+:
https://www.crunchydata.com/blog/be-ready-public-schema-changes-in-postgres-15
Need to add commands that grant the created users access to the public schema, or to avoid using the public schema at all.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is this a request for help?: No
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report
Version of Helm and Kubernetes: N/A
Which chart:
jfrog/jfrog-platform
Which product license (Enterprise/Pro/oss): N/A
JFrog support reference (if already raised with support team): N/A
What happened:
The example here:
https://github.com/jfrog/charts/blob/master/examples/jfrog-platform/docs/external-postgres.md
— is insufficient for PostgreSQL 15+, because it assumes that the public schema is globally writable, which isn't true for 15+:
https://www.crunchydata.com/blog/be-ready-public-schema-changes-in-postgres-15
Need to add commands that grant the created users access to the public schema, or to avoid using the public schema at all.
The text was updated successfully, but these errors were encountered: