Skip to content

[SQL] Clean up server update handling for soft-delete - #33933

Open
rambabu-yalla wants to merge 2 commits into
Azure:devfrom
rambabu-yalla:ramyal/FixSoftDeleteRetentionDaysUpdate
Open

[SQL] Clean up server update handling for soft-delete#33933
rambabu-yalla wants to merge 2 commits into
Azure:devfrom
rambabu-yalla:ramyal/FixSoftDeleteRetentionDaysUpdate

Conversation

@rambabu-yalla

@rambabu-yalla rambabu-yalla commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🤖 PR Validation — ❌ Action needed

Breaking Changes Tests
️✔️ None ❌ 128/130
❌AzureCLI-FullTest
️✔️acr
️✔️latest
️✔️3.12
️✔️3.14
️✔️acs
️✔️latest
️✔️3.12
️✔️3.14
️✔️advisor
️✔️latest
️✔️3.12
️✔️3.14
️✔️ams
️✔️latest
️✔️3.12
️✔️3.14
️✔️apim
️✔️latest
️✔️3.12
️✔️3.14
️✔️appconfig
️✔️latest
️✔️3.12
️✔️3.14
️✔️appservice
️✔️latest
️✔️3.12
️✔️3.14
️✔️aro
️✔️latest
️✔️3.12
️✔️3.14
️✔️backup
️✔️latest
️✔️3.12
️✔️3.14
️✔️batch
️✔️latest
️✔️3.12
️✔️3.14
️✔️batchai
️✔️latest
️✔️3.12
️✔️3.14
️✔️billing
️✔️latest
️✔️3.12
️✔️3.14
️✔️botservice
️✔️latest
️✔️3.12
️✔️3.14
️✔️cloud
️✔️latest
️✔️3.12
️✔️3.14
️✔️cognitiveservices
️✔️latest
️✔️3.12
️✔️3.14
️✔️compute_recommender
️✔️latest
️✔️3.12
️✔️3.14
️✔️computefleet
️✔️latest
️✔️3.12
️✔️3.14
️✔️config
️✔️latest
️✔️3.12
️✔️3.14
️✔️configure
️✔️latest
️✔️3.12
️✔️3.14
️✔️consumption
️✔️latest
️✔️3.12
️✔️3.14
️✔️container
️✔️latest
️✔️3.12
️✔️3.14
️✔️containerapp
️✔️latest
️✔️3.12
️✔️3.14
️✔️core
️✔️latest
️✔️3.12
️✔️3.14
️✔️cosmosdb
️✔️latest
️✔️3.12
️✔️3.14
️✔️databoxedge
️✔️latest
️✔️3.12
️✔️3.14
️✔️dls
️✔️latest
️✔️3.12
️✔️3.14
️✔️dms
️✔️latest
️✔️3.12
️✔️3.14
️✔️eventgrid
️✔️latest
️✔️3.12
️✔️3.14
️✔️eventhubs
️✔️latest
️✔️3.12
️✔️3.14
️✔️feedback
️✔️latest
️✔️3.12
️✔️3.14
️✔️find
️✔️latest
️✔️3.12
️✔️3.14
️✔️hdinsight
️✔️latest
️✔️3.12
️✔️3.14
️✔️identity
️✔️latest
️✔️3.12
️✔️3.14
️✔️iot
️✔️latest
️✔️3.12
️✔️3.14
️✔️keyvault
️✔️latest
️✔️3.12
️✔️3.14
️✔️lab
️✔️latest
️✔️3.12
️✔️3.14
️✔️managedservices
️✔️latest
️✔️3.12
️✔️3.14
️✔️maps
️✔️latest
️✔️3.12
️✔️3.14
️✔️marketplaceordering
️✔️latest
️✔️3.12
️✔️3.14
️✔️monitor
️✔️latest
️✔️3.12
️✔️3.14
️✔️mysql
️✔️latest
️✔️3.12
️✔️3.14
️✔️netappfiles
️✔️latest
️✔️3.12
️✔️3.14
️✔️network
️✔️latest
️✔️3.12
️✔️3.14
️✔️policyinsights
️✔️latest
️✔️3.12
️✔️3.14
️✔️postgresql
️✔️latest
️✔️3.12
️✔️3.14
️✔️privatedns
️✔️latest
️✔️3.12
️✔️3.14
️✔️profile
️✔️latest
️✔️3.12
️✔️3.14
️✔️rdbms
️✔️latest
️✔️3.12
️✔️3.14
️✔️redis
️✔️latest
️✔️3.12
️✔️3.14
️✔️relay
️✔️latest
️✔️3.12
️✔️3.14
️✔️resource
️✔️latest
️✔️3.12
️✔️3.14
️✔️role
️✔️latest
️✔️3.12
️✔️3.14
️✔️search
️✔️latest
️✔️3.12
️✔️3.14
️✔️security
️✔️latest
️✔️3.12
️✔️3.14
️✔️servicebus
️✔️latest
️✔️3.12
️✔️3.14
️✔️serviceconnector
️✔️latest
️✔️3.12
️✔️3.14
️✔️servicefabric
️✔️latest
️✔️3.12
️✔️3.14
️✔️signalr
️✔️latest
️✔️3.12
️✔️3.14
❌sql
❌latest
❌3.12
Type Test Case Error Message Line
Failed test_sql_server_soft_delete_retention_update_scenarios self = <azure.cli.command_modules.sql.tests.latest.test_sql_commands.SqlServerDeletedServerScenarioTest testMethod=test_sql_server_soft_delete_retention_update_scenarios>
resource_group = 'clitest.rg000001', resource_group_location = 'centralus'

    @ResourceGroupPreparer(parameter_name='resource_group', location='centralus')
    @AllowLargeResponse(size_kb=9999)
    def test_sql_server_soft_delete_retention_update_scenarios(self, resource_group, resource_group_location):
        '''
        Comprehensive test for soft delete retention days with various update scenarios.
        Tests retention_days behavior when:
        1. Server created without soft-delete, update password, then enable soft-delete
        2. Server created without soft-delete, update both soft-delete and password together
        3. Server created with soft-delete, disable soft-delete, then update password
        4. Server created with soft-delete disabled, update password, then enable soft-delete
        '''
        location = resource_group_location
        admin_login = 'admin123'
        base_password = 'SecretPassword123!'
        new_password = 'NewPassword456!'
    
        # ===== SCENARIO 1: Create without soft-delete -> Update password -> Enable soft-delete =====
        server1 = self.create_random_name('sdtest1', server_name_max_length)
    
        # Create server without soft-delete parameter
        result1 = self.cmd('sql server create -g {} --name {} -l {} --admin-user {} --admin-password {}'
                .format(resource_group, server1, location, admin_login, base_password),
                checks=[
                    JMESPathCheck('name', server1)]).get_output_in_json()
        # Validate retention_days is either -1 or 0 (both indicate not configured)
        self.assertIn(result1['retentionDays'], [-1, 0],
                     f"Expected retentionDays to be -1 or 0, got {result1['retentionDays']}")
        initial_retention = result1['retentionDays']
    
        # Update password only - retention_days should remain unchanged
        result1_updated = self.cmd('sql server update -g {} --name {} --admin-password {}'
                .format(resource_group, server1, new_password),
                checks=[
                    JMESPathCheck('name', server1)]).get_output_in_json()
        # Should remain the same as initial value
        self.assertEqual(result1_updated['retentionDays'], initial_retention,
                        f"Expected retentionDays to remain {initial_retention}, got {result1_updated['retentionDays']}")
    
        # Enable soft-delete with 5 days retention
>       self.cmd('sql server update -g {} --name {} --soft-delete-retention-days 5'
                .format(resource_group, server1),
                checks=[
                    JMESPathCheck('name', server1),
                    JMESPathCheck('retentionDays', 5)])  # Should be updated to 5

src/azure-cli/azure/cli/command_modules/sql/tests/latest/test_sql_commands.py:9842: 
                                        
src/azure-cli-testsdk/azure/cli/testsdk/base.py:177: in cmd
    return execute(self.cli_ctx, command, expect_failure=expect_failure).assert_with_checks(checks)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
src/azure-cli-testsdk/azure/cli/testsdk/base.py:278: in assert_with_checks
    c(self)
                                        

self = <azure.cli.testsdk.checkers.JMESPathCheck object at 0x7f3cc7111850>
execution_result = <azure.cli.testsdk.base.ExecutionResult object at 0x7f3cc71117c0>

    def call(self, execution_result):
        json_value = execution_result.get_output_in_json()
        actual_result = None
        try:
            actual_result = jmespath.search(self._query, json_value,
                                            jmespath.Options(collections.OrderedDict))
        except jmespath.exceptions.JMESPathTypeError:
            raise JMESPathCheckAssertionError(self._query, self._expected_result, actual_result,
                                              execution_result.output)
        if self._case_sensitive:
            equals = actual_result == self._expected_result or str(actual_result) == str(self._expected_result)
        else:
            equals = actual_result == self._expected_result <br>                or str(actual_result).lower() == str(self._expected_result).lower()
        if not equals:
            if actual_result:
>               raise JMESPathCheckAssertionError(self._query, self._expected_result, actual_result,
                                                  execution_result.output)
E               azure.cli.testsdk.exceptions.JMESPathCheckAssertionError: Query 'retentionDays' doesn't yield expected value '5', instead the actual value is '-1'. Data: 
E               {
E                 "administratorLogin": "admin123",
E                 "administratorLoginPassword": null,
E                 "administrators": null,
E                 "createMode": null,
E                 "externalGovernanceStatus": "Disabled",
E                 "federatedClientId": null,
E                 "fullyQualifiedDomainName": "sdtest1000002.database.windows.net",
E                 "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest.rg000001/providers/Microsoft.Sql/servers/sdtest1000002",
E                 "identity": null,
E                 "isIPv6Enabled": null,
E                 "keyId": null,
E                 "kind": "v12.0",
E                 "location": "westus",
E                 "minimalTlsVersion": "1.2",
E                 "name": "sdtest1000002",
E                 "primaryUserAssignedIdentityId": null,
E                 "privateEndpointConnections": [],
E                 "publicNetworkAccess": "Enabled",
E                 "resourceGroup": "clitest.rg000001",
E                 "restrictOutboundNetworkAccess": "Disabled",
E                 "retentionDays": -1,
E                 "state": "Ready",
E                 "tags": null,
E                 "type": "Microsoft.Sql/servers",
E                 "version": "12.0",
E                 "workspaceFeature": null
E               }

src/azure-cli-testsdk/azure/cli/testsdk/checkers.py:34: JMESPathCheckAssertionError
azure/cli/command_modules/sql/tests/latest/test_sql_commands.py:9802
❌3.14
Type Test Case Error Message Line
Failed test_sql_server_soft_delete_retention_update_scenarios self = <azure.cli.command_modules.sql.tests.latest.test_sql_commands.SqlServerDeletedServerScenarioTest testMethod=test_sql_server_soft_delete_retention_update_scenarios>
resource_group = 'clitest.rg000001', resource_group_location = 'centralus'

    @ResourceGroupPreparer(parameter_name='resource_group', location='centralus')
    @AllowLargeResponse(size_kb=9999)
    def test_sql_server_soft_delete_retention_update_scenarios(self, resource_group, resource_group_location):
        '''
        Comprehensive test for soft delete retention days with various update scenarios.
        Tests retention_days behavior when:
        1. Server created without soft-delete, update password, then enable soft-delete
        2. Server created without soft-delete, update both soft-delete and password together
        3. Server created with soft-delete, disable soft-delete, then update password
        4. Server created with soft-delete disabled, update password, then enable soft-delete
        '''
        location = resource_group_location
        admin_login = 'admin123'
        base_password = 'SecretPassword123!'
        new_password = 'NewPassword456!'
    
        # ===== SCENARIO 1: Create without soft-delete -> Update password -> Enable soft-delete =====
        server1 = self.create_random_name('sdtest1', server_name_max_length)
    
        # Create server without soft-delete parameter
        result1 = self.cmd('sql server create -g {} --name {} -l {} --admin-user {} --admin-password {}'
                .format(resource_group, server1, location, admin_login, base_password),
                checks=[
                    JMESPathCheck('name', server1)]).get_output_in_json()
        # Validate retention_days is either -1 or 0 (both indicate not configured)
        self.assertIn(result1['retentionDays'], [-1, 0],
                     f"Expected retentionDays to be -1 or 0, got {result1['retentionDays']}")
        initial_retention = result1['retentionDays']
    
        # Update password only - retention_days should remain unchanged
        result1_updated = self.cmd('sql server update -g {} --name {} --admin-password {}'
                .format(resource_group, server1, new_password),
                checks=[
                    JMESPathCheck('name', server1)]).get_output_in_json()
        # Should remain the same as initial value
        self.assertEqual(result1_updated['retentionDays'], initial_retention,
                        f"Expected retentionDays to remain {initial_retention}, got {result1_updated['retentionDays']}")
    
        # Enable soft-delete with 5 days retention
>       self.cmd('sql server update -g {} --name {} --soft-delete-retention-days 5'
                .format(resource_group, server1),
                checks=[
                    JMESPathCheck('name', server1),
                    JMESPathCheck('retentionDays', 5)])  # Should be updated to 5

src/azure-cli/azure/cli/command_modules/sql/tests/latest/test_sql_commands.py:9842: 
                                        
src/azure-cli-testsdk/azure/cli/testsdk/base.py:177: in cmd
    return execute(self.cli_ctx, command, expect_failure=expect_failure).assert_with_checks(checks)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
src/azure-cli-testsdk/azure/cli/testsdk/base.py:278: in assert_with_checks
    c(self)
                                        

self = <azure.cli.testsdk.checkers.JMESPathCheck object at 0x7fd41349a9c0>
execution_result = <azure.cli.testsdk.base.ExecutionResult object at 0x7fd413b4c910>

    def call(self, execution_result):
        json_value = execution_result.get_output_in_json()
        actual_result = None
        try:
            actual_result = jmespath.search(self._query, json_value,
                                            jmespath.Options(collections.OrderedDict))
        except jmespath.exceptions.JMESPathTypeError:
            raise JMESPathCheckAssertionError(self._query, self._expected_result, actual_result,
                                              execution_result.output)
        if self._case_sensitive:
            equals = actual_result == self._expected_result or str(actual_result) == str(self._expected_result)
        else:
            equals = actual_result == self._expected_result <br>                or str(actual_result).lower() == str(self._expected_result).lower()
        if not equals:
            if actual_result:
>               raise JMESPathCheckAssertionError(self._query, self._expected_result, actual_result,
                                                  execution_result.output)
E               azure.cli.testsdk.exceptions.JMESPathCheckAssertionError: Query 'retentionDays' doesn't yield expected value '5', instead the actual value is '-1'. Data: 
E               {
E                 "administratorLogin": "admin123",
E                 "administratorLoginPassword": null,
E                 "administrators": null,
E                 "createMode": null,
E                 "externalGovernanceStatus": "Disabled",
E                 "federatedClientId": null,
E                 "fullyQualifiedDomainName": "sdtest1000002.database.windows.net",
E                 "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest.rg000001/providers/Microsoft.Sql/servers/sdtest1000002",
E                 "identity": null,
E                 "isIPv6Enabled": null,
E                 "keyId": null,
E                 "kind": "v12.0",
E                 "location": "westus",
E                 "minimalTlsVersion": "1.2",
E                 "name": "sdtest1000002",
E                 "primaryUserAssignedIdentityId": null,
E                 "privateEndpointConnections": [],
E                 "publicNetworkAccess": "Enabled",
E                 "resourceGroup": "clitest.rg000001",
E                 "restrictOutboundNetworkAccess": "Disabled",
E                 "retentionDays": -1,
E                 "state": "Ready",
E                 "tags": null,
E                 "type": "Microsoft.Sql/servers",
E                 "version": "12.0",
E                 "workspaceFeature": null
E               }

src/azure-cli-testsdk/azure/cli/testsdk/checkers.py:34: JMESPathCheckAssertionError
azure/cli/command_modules/sql/tests/latest/test_sql_commands.py:9802
️✔️sqlvm
️✔️latest
️✔️3.12
️✔️3.14
️✔️storage
️✔️latest
️✔️3.12
️✔️3.14
️✔️synapse
️✔️latest
️✔️3.12
️✔️3.14
️✔️telemetry
️✔️latest
️✔️3.12
️✔️3.14
️✔️util
️✔️latest
️✔️3.12
️✔️3.14
️✔️vm
️✔️latest
️✔️3.12
️✔️3.14

Related command

az sql server update,

Description

No customer-facing behavior change

  1. az sql server update: Removed custom handling of --soft-delete-retention-days and switched to the standard update pattern. Previously the update path unconditionally reassigned instance.retention_days, which caused the PUT body to carry an empty retention value on unrelated updates. The SQL RP discards null, so nothing was actually reset — this just stops the CLI from round-tripping stale state.

Testing Guide

No commands are updated

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature


This checklist is used to make sure that common guidelines for a pull request are followed.

@rambabu-yalla
rambabu-yalla requested a review from a team as a code owner August 19, 2026 17:36
Copilot AI lite review requested due to automatic review settings August 19, 2026 17:36
@azure-client-tools-bot-prd

Copy link
Copy Markdown

Hi rambabu-yalla,
Since the current milestone time is less than 7 days, this pr may not catch up with this release.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Azure SQL command module internals to preserve retentionDays (soft-delete retention) during az sql server update when --soft-delete-retention-days is not provided, and adjusts deleted-server listing behavior/tests and their recordings accordingly.

Changes:

  • Update server_update to preserve the existing retentionDays value unless --soft-delete-retention-days is explicitly passed.
  • Adjust deleted_server_list to treat an explicitly provided empty --location "" as “location-scoped” (instead of falling back to subscription-wide listing).
  • Refresh/strengthen SQL soft-delete tests and update associated recordings (including location changes and updated CLI/sdk metadata).

Reviewed changes

Copilot reviewed 6 out of 20 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
src/azure-cli/azure/cli/command_modules/sql/custom.py Preserves retentionDays on update; changes deleted-server list branching for location.
src/azure-cli/azure/cli/command_modules/sql/tests/latest/test_sql_commands.py Updates/expands soft-delete lifecycle tests and adjusts test locations/expectations.
src/azure-cli/azure/cli/command_modules/sql/tests/latest/recordings/test_sql_server_create_without_soft_delete.yaml Updates recording for create-without-soft-delete scenario (westus + updated headers/timestamps).
src/azure-cli/azure/cli/command_modules/sql/tests/latest/recordings/test_sql_deleted_server_show_not_found.yaml Updates recording headers/timestamps for deleted-server show-not-found.
src/azure-cli/azure/cli/command_modules/sql/tests/latest/recordings/test_sql_deleted_server_list_empty_location.yaml Updates recording payload and metadata for deleted-server list scenario.
Suppressed comments (1)

src/azure-cli/azure/cli/command_modules/sql/custom.py:4458

  • The new location is not None behavior is intended to change how --location "" behaves, but there is no test asserting that the CLI fails fast with a clear error for an empty location value.
    if location is not None:
        return client.list_by_location(location)

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines 4454 to 4459
# Use `is not None` so that an explicitly provided empty string (e.g. --location "")
# keeps location-scoped behavior and fails fast at the API, rather than silently
# switching to the subscription-wide listing.
if location is not None:
return client.list_by_location(location)
return client.list()
@rambabu-yalla rambabu-yalla changed the title {SQL} Preserve soft-delete-retention-days on server update and add validation for deleted-server command {SQL} Clean up server update and deleted-server list handling for soft-delete Aug 19, 2026
@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@rambabu-yalla
rambabu-yalla force-pushed the ramyal/FixSoftDeleteRetentionDaysUpdate branch from ae8bafa to 70f2992 Compare August 19, 2026 19:35
@rambabu-yalla rambabu-yalla changed the title {SQL} Clean up server update and deleted-server list handling for soft-delete [SQL] Clean up server update and deleted-server list handling for soft-delete Aug 19, 2026
@rambabu-yalla rambabu-yalla changed the title [SQL] Clean up server update and deleted-server list handling for soft-delete [SQL] Clean up server update handling for soft-delete Aug 19, 2026
@rambabu-yalla
rambabu-yalla requested a lite review from Copilot August 19, 2026 19:38

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 3 out of 11 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/azure-cli/azure/cli/command_modules/sql/tests/latest/test_sql_commands.py:9469

  • The test now asserts retentionDays == -1 on create/show, but elsewhere in this same file test_sql_server_soft_delete_retention_update_scenarios explicitly treats retentionDays as -1 or 0 when soft delete was not configured. This stricter expectation can make the test flaky across RP/API-version variations and is inconsistent with the existing test semantics; consider asserting membership in [-1, 0, None] instead of a fixed -1.
                     JMESPathCheck('retentionDays', -1)])

        # Verify via show as well: retentionDays must be -1 (never configured)
        self.cmd('sql server show -g {} --name {}'
                 .format(resource_group, server_name),

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@azure-client-tools-agent

Copy link
Copy Markdown
Contributor

Live test results — azdev test --live --series (changed test files only)

⚠️ NO TESTS SELECTED — changed test files did not resolve to runnable tests

Selectors: test_sql_commands (module)
PR head ref: ramyal/FixSoftDeleteRetentionDaysUpdate
PR head sha: 70f2992eb7374ca2f719f541cfd09f922cfec600
PR base ref: dev
New test files in PR: false

Changed test files run
src/azure-cli/azure/cli/command_modules/sql/tests/latest/test_sql_commands.py

Workflow run: https://github.com/Azure/issue-sentinel/actions/runs/32331632573

Last 80 lines of azdev output

=============
| Run Tests |
=============


=====================
| Discovering Tests |
=====================

/home/runner/work/issue-sentinel/issue-sentinel/azure-cli/src/azure-cli/azure/cli/command_modules/vm/tests/latest/test_vm_commands.py:13640: SyntaxWarning: invalid escape sequence '\]'
  self.cmd('vmss application set -g {rg} -n {vmss} --app-version-ids {vid1} {vid2} --enable-automatic-upgrade True\]', checks=[
/home/runner/work/issue-sentinel/issue-sentinel/azure-cli/src/azure-cli/azure/cli/command_modules/identity/tests/latest/test_identity.py:18: SyntaxWarning: invalid escape sequence '\{'
  'resource_restriction_compute': '\{"providers":\["Microsoft.Compute"\]\}',
/home/runner/work/issue-sentinel/issue-sentinel/azure-cli/src/azure-cli/azure/cli/command_modules/identity/tests/latest/test_identity.py:19: SyntaxWarning: invalid escape sequence '\{'
  'resource_restriction_empty': '\{"providers":\[\]\}'
WARNING: 'test_sql_commands' exists in both 'sql' and 'backup'. Resolve using `sql.test_sql_commands` or `backup.test_sql_commands`Duplication exists in: 
	/home/runner/work/issue-sentinel/issue-sentinel/azure-cli/src/azure-cli/azure/cli/command_modules/sql/tests/latest/test_sql_commands.py
	/home/runner/work/issue-sentinel/issue-sentinel/azure-cli/src/azure-cli/azure/cli/command_modules/backup/tests/latest/test_sql_commands.py


test index updated: /home/runner/.azdev/env_config/home/runner/work/issue-sentinel/issue-sentinel/.venv/test_index/latest.json

Test on modules: test_sql_commands

WARNING: RUNNING TESTS LIVE
WARNING: 'test_sql_commands' not found. If newly added, re-run with --discover
WARNING: No tests selected to run.

Posted by agent-assist live-test workflow.

@azure-client-tools-agent azure-client-tools-agent Bot added the azure-client-tools-agent Pull request reviewed by Azure Client Tools Agent label Aug 20, 2026

@azure-client-tools-agent azure-client-tools-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validation Summary

Automated checks found failures on the current head commit (70f2992):

CI (GitHub Actions):

  • Azure.azure-cli Full Test — build failed (run)
  • Azure.azure-cli — build failed (run)
  • Azure.azure-cli Full Test (Automation Full Test Python314 Profile Latest instance5) — failed (run)
  • Azure.azure-cli Full Test (Automation Full Test Python312 Profile Latest instance5) — failed (run)
  • ✅ 48/53 other checks passed

Live test (azdev test --live): ❌ failed (run)

please take a look at the failing builds/tests linked above and push a fix. Re-request review once addressed.

@azure-client-tools-agent azure-client-tools-agent Bot removed the Azure Client Tools Agent Requested Request Azure Client Tools Agent testing and review label Aug 20, 2026
@microsoft-github-policy-service

Copy link
Copy Markdown
Contributor

🔔 Routing this PR to @Azure/act-codegen-extensibility-squad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

act-codegen-extensibility-squad Auto-Assign Auto assign by bot azure-client-tools-agent Pull request reviewed by Azure Client Tools Agent SQL az sql

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants