Skip to content
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

Open
1 task done
Carus11 opened this issue Jan 10, 2025 · 4 comments · May be fixed by #425
Open
1 task done

2024.12 introduces additional required external-pg extension #423

Carus11 opened this issue Jan 10, 2025 · 4 comments · May be fixed by #425
Labels
bug Something isn't working new Added to an issue when it's new ;)

Comments

@Carus11
Copy link

Carus11 commented Jan 10, 2025

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

  • I agree to follow this project's Code of Conduct
@Carus11 Carus11 added bug Something isn't working new Added to an issue when it's new ;) labels Jan 10, 2025
@Carus11 Carus11 changed the title 2024.12 introduces additional required pg extension 2024.12 introduces additional required external-pg extension Jan 10, 2025
@Carus11
Copy link
Author

Carus11 commented Jan 10, 2025

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"
}

@dhoucgitter
Copy link
Member

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

For Viya 4 Cadences 2024.06 and later: SharedServices Database Creation Behavior Change

For Viya 4 Cadences 2024.06 and later, the sas-data-server-operator will not automatically create the SharedServices database in an External Postgres database instance during the initial deployment of the SAS Viya platform. Instead, you must manually create the SharedServices database before you start the SAS Viya platform deployment using viya4-deployment Release 7.0.0 or later.

@jeread jeread linked a pull request Jan 14, 2025 that will close this issue
@dhoucgitter
Copy link
Member

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 ?

@Carus11
Copy link
Author

Carus11 commented Jan 14, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working new Added to an issue when it's new ;)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants