-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
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
2024.12 introduces additional required external-pg extension #423
Comments
Looks like at https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/postgresql_flexible_server_configuration We could pass a comma separated list resource "azurerm_postgresql_flexible_server_configuration" "example" {
name = "azure.extensions"
server_id = azurerm_postgresql_flexible_server.example.id
value = "CUBE,CITEXT,BTREE_GIST"
} |
Hi @Carus11, the deployment issue you are seeing with DaC and Viya 2024.12 could also be related to the breaking change documented here https://github.com/sassoftware/viya4-deployment/releases/tag/7.0.0
|
Hi @carus1, given that this is a Viya 2024.12 requirement, the expectation is that all external postgres instances, whether in Azure, AWS or GCP will require similar support regarding encryption. Would you agree that is the case given the SAS doc you linked to above https://go.documentation.sas.com/doc/en/sasadmincdc/v_059/itopssr/p05lfgkwib3zxbn1t6nyihexp12n.htm ? |
Yes, its a platform pre-install requirement now. I am unaware if it is a default extension anywhere else, or if it need to be explicitly added. |
Terraform Version Details
No response
Terraform Variable File Details
No response
Steps to Reproduce
Deploy IAC and then Viya 2024.12 with external PG
Expected Behavior
The deployment with external postgresql should work
Actual Behavior
It fails because of missing pg extensions
Additional Context
Looks like it may be the pgcrypto extension
https://go.documentation.sas.com/doc/en/sasadmincdc/v_059/itopssr/p05lfgkwib3zxbn1t6nyihexp12n.htm
References
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: