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

ServerPropertiesForReplica.publicNetworkAccess = Disabled is not persisted on create Postgresql Single Server Replica #14117

Open
aristosvo opened this issue Apr 25, 2021 · 1 comment
Labels
PostgreSQL question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@aristosvo
Copy link

aristosvo commented Apr 25, 2021

Problem

publicNetworkAccess is not persisted when calling to create a Replica PostgreSQL Single Server and publicNetorkAccess is specified in ServerPropertiesForReplica (docs)

How to reproduce it

From the logs:
PUT /subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083-replica/providers/Microsoft.DBForPostgreSQL/servers/acctest-psql-server-210425092555925083-replica?api-version=2017-12-01 HTTP/1.1

{
    "location": "westeurope",
    "properties": {
        "createMode": "Replica",
        "infrastructureEncryption": "Disabled",
        "minimalTlsVersion": "TLSEnforcementDisabled",
        "publicNetworkAccess": "Disabled",
        "sourceServerId": "/subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083/providers/Microsoft.DBforPostgreSQL/servers/acctest-psql-server-210425092555925083",
        "sslEnforcement": "Enabled",
        "version": "11"
    },
    "sku": {
        "name": "GP_Gen5_2",
        "tier": "GeneralPurpose",
        "capacity": 2,
        "family": "Gen5"
    },
    "tags": {}
}

GET /subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083-replica/providers/Microsoft.DBForPostgreSQL/servers/acctest-psql-server-210425092555925083-replica?api-version=2017-12-01 HTTP/1.1

{
    "sku": {
        "name": "GP_Gen5_2",
        "tier": "GeneralPurpose",
        "family": "Gen5",
        "capacity": 2
    },
    "properties": {
        "administratorLogin": "acctestun",
        "storageProfile": {
            "storageMB": 51200,
            "backupRetentionDays": 7,
            "geoRedundantBackup": "Disabled",
            "storageAutogrow": "Enabled"
        },
        "version": "11",
        "sslEnforcement": "Enabled",
        "minimalTlsVersion": "TLSEnforcementDisabled",
        "userVisibleState": "Ready",
        "fullyQualifiedDomainName": "acctest-psql-server-210425092555925083-replica.postgres.database.azure.com",
        "earliestRestoreDate": "2021-04-25T07:39:38.66+00:00",
        "replicationRole": "Replica",
        "masterServerId": "/subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083/providers/Microsoft.DBforPostgreSQL/servers/acctest-psql-server-210425092555925083",
        "replicaCapacity": 0,
        "byokEnforcement": "Disabled",
        "privateEndpointConnections": [],
        "infrastructureEncryption": "Disabled",
        "publicNetworkAccess": "Enabled"
    },
    "location": "westeurope",
    "tags": {},
    "id": "/subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083-replica/providers/Microsoft.DBforPostgreSQL/servers/acctest-psql-server-210425092555925083-replica",
    "name": "acctest-psql-server-210425092555925083-replica",
    "type": "Microsoft.DBforPostgreSQL/servers"
}
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 25, 2021
@leni-msft leni-msft added PostgreSQL Service Attention Workflow: This issue is responsible by Azure service team. labels May 3, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 3, 2021
@ghost
Copy link

ghost commented May 3, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sunilagarwal, @lfittl-msft, @sr-msft, @niklarin.

Issue Details

Problem

publicNetworkAccess is not persisted when calling to create a Replica PostgreSQL Single Server and publicNetorkAccess is specified in ServerPropertiesForReplica (docs)

How to reproduce it

From the logs:
PUT /subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083-replica/providers/Microsoft.DBForPostgreSQL/servers/acctest-psql-server-210425092555925083-replica?api-version=2017-12-01 HTTP/1.1

{
    "location": "westeurope",
    "properties": {
        "createMode": "Replica",
        "infrastructureEncryption": "Disabled",
        "minimalTlsVersion": "TLSEnforcementDisabled",
        "publicNetworkAccess": "Disabled",
        "sourceServerId": "/subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083/providers/Microsoft.DBforPostgreSQL/servers/acctest-psql-server-210425092555925083",
        "sslEnforcement": "Enabled",
        "version": "11"
    },
    "sku": {
        "name": "GP_Gen5_2",
        "tier": "GeneralPurpose",
        "capacity": 2,
        "family": "Gen5"
    },
    "tags": {}
}

GET /subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083-replica/providers/Microsoft.DBForPostgreSQL/servers/acctest-psql-server-210425092555925083-replica?api-version=2017-12-01 HTTP/1.1

{
    "sku": {
        "name": "GP_Gen5_2",
        "tier": "GeneralPurpose",
        "family": "Gen5",
        "capacity": 2
    },
    "properties": {
        "administratorLogin": "acctestun",
        "storageProfile": {
            "storageMB": 51200,
            "backupRetentionDays": 7,
            "geoRedundantBackup": "Disabled",
            "storageAutogrow": "Enabled"
        },
        "version": "11",
        "sslEnforcement": "Enabled",
        "minimalTlsVersion": "TLSEnforcementDisabled",
        "userVisibleState": "Ready",
        "fullyQualifiedDomainName": "acctest-psql-server-210425092555925083-replica.postgres.database.azure.com",
        "earliestRestoreDate": "2021-04-25T07:39:38.66+00:00",
        "replicationRole": "Replica",
        "masterServerId": "/subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083/providers/Microsoft.DBforPostgreSQL/servers/acctest-psql-server-210425092555925083",
        "replicaCapacity": 0,
        "byokEnforcement": "Disabled",
        "privateEndpointConnections": [],
        "infrastructureEncryption": "Disabled",
        "publicNetworkAccess": "Enabled"
    },
    "location": "westeurope",
    "tags": {},
    "id": "/subscriptions/***/resourceGroups/acctestRG-psql-210425092555925083-replica/providers/Microsoft.DBforPostgreSQL/servers/acctest-psql-server-210425092555925083-replica",
    "name": "acctest-psql-server-210425092555925083-replica",
    "type": "Microsoft.DBforPostgreSQL/servers"
}
Author: aristosvo
Assignees: akning-ms
Labels:

PostgreSQL, Service Attention, needs-triage, question

Milestone: -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PostgreSQL question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants