-
Notifications
You must be signed in to change notification settings - Fork 394
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
[AVM Module Issue]: postgres flexible replica server error on property fullyQualifiedDomainName #4249
Comments
Important The "Needs: Triage 🔍" label must be removed once the triage process is complete! Tip For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation. |
@thllxb, thanks for submitting this issue for the Important A member of the @Azure/avm-res-dbforpostgresql-flexibleserver-module-owners-bicep or @Azure/avm-res-dbforpostgresql-flexibleserver-module-contributors-bicep team will review it soon! |
FYI, Bicep CLI version 0.32.4 (b326faa456) |
Though the bicep deployment ends with error, the resource (the replica server) gets created successfully. Ironically, on the azure portal, the resource clearly presents the |
Currently under investigation in collaboration with the PostgreSQL Flexible Server product group. |
I have been able to recreate the same issue outside of the PostgreSQL Flexible Server AVM module. I have turned over my findings and sample code to the PostgreSQL Flexible Server product group. |
Check for previous/existing GitHub issues
Issue Type?
Bug
Module Name
avm/res/db-for-postgre-sql/flexible-server
(Optional) Module Version
0.7.1
Description
When creating a postgre flexible server in replica mode, it returns an error saying the property
fullyQualifiedDomainName
doesnt exist.[{"code":"DeploymentOutputEvaluationFailed","target":"fqdn","message":"The template output 'fqdn' is not valid: The language expression property 'fullyQualifiedDomainName' doesn't exist, available properties are 'replica, storage, network, dataEncryption, state, backup, replicationRole'.."}]
example code:
(Optional) Correlation Id
No response
The text was updated successfully, but these errors were encountered: