Skip to content

Commit 0bebc4e

Browse files
committed
fix cosmosdb restore test where a future time is incorrectly used
1 parent e63b732 commit 0bebc4e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/azure-cli/azure/cli/command_modules/cosmosdb/tests/latest/test_cosmosdb_commands.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2085,7 +2085,7 @@ def test_cosmosdb_restore_command(self, resource_group, location):
20852085

20862086
import dateutil.parser
20872087
import time
2088-
from datetime import timedelta
2088+
from datetime import timedelta, datetime
20892089

20902090
# This should fail as restore time is before account creation time
20912091
invalid_restore_time = dateutil.parser.parse(restorable_database_account['creationTime']) - timedelta(days=30)
@@ -2095,7 +2095,7 @@ def test_cosmosdb_restore_command(self, resource_group, location):
20952095
self.assertRaises(Exception, lambda: self.cmd('az cosmosdb restore --account-name {acc} -g {rg} --restore-timestamp {invalid_restore_time} --location {loc} --target-database-account-name {restored_acc}'))
20962096

20972097
# This should fail as restore time is in future
2098-
invalid_restore_time = dateutil.parser.parse(restorable_database_account['creationTime']) + timedelta(days=30)
2098+
invalid_restore_time = datetime.now() + timedelta(days=30)
20992099
self.kwargs.update({
21002100
'invalid_restore_time': invalid_restore_time.isoformat()
21012101
})

0 commit comments

Comments
 (0)