-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[SQL] az sql midb log-replay: Support for log replay service on managed database #15168
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
Changes from all commits
00b9235
ab16df0
03436bc
7d98b1f
06f6ec5
adab2d2
c7b9f98
18e8b8d
1eb5074
cc3a159
af8f98e
0f904b9
9968e6d
c8abe60
9c48068
a4192ea
702eeaa
d17a993
73a9256
9791b52
3be9b07
ff39850
a78f79a
5294f88
0c67b16
494ce40
caa3e0c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -42,6 +42,7 @@ | |
| get_sql_firewall_rules_operations, | ||
| get_sql_instance_pools_operations, | ||
| get_sql_managed_databases_operations, | ||
| get_sql_managed_database_restore_details_operations, | ||
| get_sql_managed_backup_short_term_retention_policies_operations, | ||
| get_sql_managed_database_long_term_retention_policies_operations, | ||
| get_sql_managed_database_long_term_retention_backups_operations, | ||
|
|
@@ -703,6 +704,24 @@ def load_command_table(self, _): | |
| is_preview=True) | ||
| g.wait_command('wait') | ||
|
|
||
| with self.command_group('sql midb log-replay', | ||
| managed_databases_operations, | ||
| client_factory=get_sql_managed_databases_operations) as g: | ||
| g.custom_command('start', 'managed_db_log_replay_start', supports_no_wait=True) | ||
| g.command('stop', 'delete', confirmation=True, supports_no_wait=True) | ||
| g.command('complete', 'complete_restore') | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please add wait command here
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added, but can you tell what is the use case for wait command? Why am I adding it (there must be some rule that I am not aware of ) ?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. because you support no wait for some commands, e.g. start, stop, if users use --no-wait in your command, the command will not wait any more. But if i want to query command status, i have to use wait command
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh okay I get it now. Thanks |
||
| g.wait_command('wait') | ||
|
|
||
| managed_database_restore_details_operations = CliCommandType( | ||
| operations_tmpl='azure.mgmt.sql.operations#ManagedDatabaseRestoreDetailsOperations.{}', | ||
| client_factory=get_sql_managed_database_restore_details_operations) | ||
|
|
||
| with self.command_group('sql midb log-replay', | ||
| managed_database_restore_details_operations, | ||
| client_factory=get_sql_managed_database_restore_details_operations) as g: | ||
|
|
||
| g.show_command('show', 'get') | ||
|
|
||
| ############################################### | ||
| # sql virtual cluster # | ||
| ############################################### | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.