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

Template violation when using pgserver.FullyQualifiedDomainName in setting #1139

Open
Janna112358 opened this issue Oct 11, 2024 · 3 comments · May be fixed by #1140
Open

Template violation when using pgserver.FullyQualifiedDomainName in setting #1139

Janna112358 opened this issue Oct 11, 2024 · 3 comments · May be fixed by #1140
Assignees
Labels
bug Something isn't working

Comments

@Janna112358
Copy link

I ran into this using code based on "webapp pg farmer sample" so I opened the issue there originally :)

Farmer version: 1.8.13

@isaacabraham
Copy link
Member

Hey @Janna112358 could you send a slightly more complete sample - I think I have a fix, but ideally would like to do an end-to-end test before releasing a fix.

@isaacabraham isaacabraham added the bug Something isn't working label Oct 11, 2024
@isaacabraham isaacabraham self-assigned this Oct 11, 2024
@isaacabraham
Copy link
Member

You can also test this yourself:

type PostgreSQLConfig with
    member this.FixedFqdn =
        ArmExpression
            .reference(Farmer.Arm.DBforPostgreSQL.servers.resourceId this.Name)
            .Map(fun r -> r + ".fullyQualifiedDomainName")
            .Eval()

If you can confirm that this works, I'm happy to push it directly without an end-to-end test myself.

@isaacabraham
Copy link
Member

Ok on further inspection there were a few issues left from the move to flexible servers that I've now fixed.

@isaacabraham isaacabraham linked a pull request Oct 13, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants