You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Note**: New MongoDB Databases cannot currently be created.
3221
3222
security:
3222
3223
- personalAccessToken: []
3223
3224
- oauth:
@@ -3246,99 +3247,99 @@ paths:
3246
3247
- lang: CLI
3247
3248
source: >
3248
3249
linode-cli databases mongodb-list
3249
-
post:
3250
-
tags:
3251
-
- Databases
3252
-
summary: Managed MongoDB Database Create
3253
-
operationId: postDatabasesMongoDBInstances
3254
-
servers:
3255
-
- url: https://api.linode.com/v4
3256
-
- url: https://api.linode.com/v4beta
3257
-
x-linode-cli-action: mongodb-create
3258
-
x-linode-grant: add_databases
3259
-
description: |
3260
-
Provision a Managed MongoDB Database.
3261
-
3262
-
Restricted Users must have the `add_databases` grant to use this command.
3263
-
3264
-
New instances can take approximately 15 to 30 minutes to provision.
3265
-
3266
-
The `allow_list` is used to control access to the Managed Database.
3267
-
3268
-
* IP addresses on this list can access the Managed Database. All other sources are blocked.
3269
-
* Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database.
3270
-
3271
-
All Managed Databases include automatic, daily backups. Up to seven backups are automatically stored for each Managed Database, providing restore points for each day of the past week.
3272
-
3273
-
All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed MongoDB Database during configurable maintenance windows.
3274
-
3275
-
* If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance.
3276
-
3277
-
* **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.
3278
-
3279
-
* To modify update the maintenance window for a Database, use the **Managed MongoDB Database Update** ([PUT /databases/mongodb/instances/{instanceId}](/docs/api/databases/#managed-mongodb-database-update)) command.
3280
-
3281
-
**Note**: Managed MongoDB clusters are currently accessible over public IP addresses. To provide an additional layer of protection, support for private IP addresses is in development.
3282
-
security:
3283
-
- personalAccessToken: []
3284
-
- oauth:
3285
-
- databases:read_write
3286
-
requestBody:
3287
-
description: Information about the Managed MongoDB Database you are creating.
# Restricted Users must have the `add_databases` grant to use this command.
3264
+
3265
+
# New instances can take approximately 15 to 30 minutes to provision.
3266
+
3267
+
# The `allow_list` is used to control access to the Managed Database.
3268
+
3269
+
# * IP addresses on this list can access the Managed Database. All other sources are blocked.
3270
+
# * Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database.
3271
+
3272
+
# All Managed Databases include automatic, daily backups. Up to seven backups are automatically stored for each Managed Database, providing restore points for each day of the past week.
3273
+
3274
+
# All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed MongoDB Database during configurable maintenance windows.
3275
+
3276
+
# * If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance.
3277
+
3278
+
# * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.
3279
+
3280
+
# * To modify update the maintenance window for a Database, use the **Managed MongoDB Database Update** ([PUT /databases/mongodb/instances/{instanceId}](/docs/api/databases/#managed-mongodb-database-update)) command.
3281
+
3282
+
# **Note**: Managed MongoDB clusters are currently accessible over public IP addresses. To provide an additional layer of protection, support for private IP addresses is in development.
3283
+
# security:
3284
+
# - personalAccessToken: []
3285
+
# - oauth:
3286
+
# - databases:read_write
3287
+
# requestBody:
3288
+
# description: Information about the Managed MongoDB Database you are creating.
Display information for a single, accessible Managed MongoDB Database.
3364
+
**Note**: New MongoDB Databases cannot currently be created.
3363
3365
security:
3364
3366
- personalAccessToken: []
3365
3367
- oauth:
@@ -3393,12 +3395,10 @@ paths:
3393
3395
x-linode-grant: read_write
3394
3396
description: |
3395
3397
Remove a Managed MongoDB Database from your Account.
3396
-
3397
3398
Requires `read_write` access to the Database.
3398
-
3399
3399
The Database must have an `active`, `failed`, or `degraded` status to perform this command.
3400
-
3401
3400
Only unrestricted Users can access this command, and have access regardless of the acting token's OAuth scopes.
3401
+
**Note**: New MongoDB Databases cannot currently be created.
3402
3402
security:
3403
3403
- personalAccessToken: []
3404
3404
- oauth:
@@ -3433,22 +3433,16 @@ paths:
3433
3433
x-linode-grant: read_write
3434
3434
description: |
3435
3435
Update a Managed MongoDB Database.
3436
-
3437
3436
Requires `read_write` access to the Database.
3438
-
3439
3437
The Database must have an `active` status to perform this command.
3440
-
3441
3438
Updating addresses in the `allow_list` overwrites any existing addresses.
3442
-
3443
3439
* IP addresses on this list can access the Managed Database. All other sources are blocked.
3444
3440
* Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database.
3445
3441
* **Note**: Updates to the `allow_list` may take a short period of time to complete, making this command inappropriate for rapid successive updates to this property.
3446
-
3447
3442
All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed MongoDB Database. The maintenance window for these updates is configured with the Managed Database's `updates` property.
3448
-
3449
3443
* If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance.
3450
-
3451
3444
* **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.
3445
+
**Note**: New MongoDB Databases cannot currently be created.
3452
3446
security:
3453
3447
- personalAccessToken: []
3454
3448
- oauth:
@@ -3532,12 +3526,10 @@ paths:
3532
3526
- $ref: '#/components/parameters/pageSize'
3533
3527
description: |
3534
3528
Display all backups for an accessible Managed MongoDB Database.
3535
-
3536
3529
The Database must not be provisioning to perform this command.
3537
-
3538
3530
Database `auto` type backups are created every 24 hours at 0:00 UTC. Each `auto` backup is retained for 7 days.
3539
-
3540
3531
Database `snapshot` type backups are created by accessing the **Managed MongoDB Database Backup Snapshot Create** ([POST /databases/mongodb/instances/{instanceId}/backups](/docs/api/databases/#managed-mongodb-database-backup-snapshot-create)) command.
3532
+
**Note**: New MongoDB Databases cannot currently be created.
3541
3533
security:
3542
3534
- personalAccessToken: []
3543
3535
- oauth:
@@ -3578,12 +3570,10 @@ paths:
3578
3570
x-linode-grant: read_write
3579
3571
description: |
3580
3572
Creates a snapshot backup of a Managed MongoDB Database.
3581
-
3582
3573
Requires `read_write` access to the Database.
3583
-
3584
3574
Backups generated by this command have the type `snapshot`. Snapshot backups may take several minutes to complete, after which they will be accessible to view or restore.
3585
-
3586
3575
The Database must have an `active` status to perform this command.
3576
+
**Note**: New MongoDB Databases cannot currently be created.
3587
3577
security:
3588
3578
- personalAccessToken: []
3589
3579
- oauth:
@@ -3603,7 +3593,6 @@ paths:
3603
3593
maxLength: 64
3604
3594
description: |
3605
3595
The label for the Database snapshot backup.
3606
-
3607
3596
* Must use only letters, numbers, underscores, dashes, and periods.
3608
3597
* Must begin and end with a letter or number.
3609
3598
* Must not include two dashes, underscores, or periods in a row.
@@ -3616,7 +3605,6 @@ paths:
3616
3605
default: primary
3617
3606
description: |
3618
3607
The Database cluster target.
3619
-
3620
3608
If the Database is a high availability cluster, choosing `secondary` creates a snapshot backup of a replica node.
3621
3609
example: primary
3622
3610
responses:
@@ -3669,8 +3657,8 @@ paths:
3669
3657
x-linode-grant: read_only
3670
3658
description: |
3671
3659
Display information for a single backup for an accessible Managed MongoDB Database.
3672
-
3673
3660
The Database must not be provisioning to perform this command.
3661
+
**Note**: New MongoDB Databases cannot currently be created.
3674
3662
security:
3675
3663
- personalAccessToken: []
3676
3664
- oauth:
@@ -3704,10 +3692,9 @@ paths:
3704
3692
x-linode-grant: unrestricted only
3705
3693
description: |
3706
3694
Delete a single backup for an accessible Managed MongoDB Database.
3707
-
3708
3695
Requires `read_write` access to the Database.
3709
-
3710
3696
The Database must not be provisioning to perform this command.
3697
+
**Note**: New MongoDB Databases cannot currently be created.
3711
3698
security:
3712
3699
- personalAccessToken: []
3713
3700
- oauth:
@@ -3757,14 +3744,11 @@ paths:
3757
3744
x-linode-grant: read_write
3758
3745
description: |
3759
3746
Restore a backup to a Managed MongoDB Database on your Account.
3760
-
3761
3747
Requires `read_write` access to the Database.
3762
-
3763
3748
The Database must have an `active` status to perform this command.
3764
-
3765
3749
**Note**: Restoring from a backup will erase all existing data on the database instance and replace it with backup data.
3766
-
3767
3750
**Note**: Currently, restoring a backup after resetting Managed Database credentials results in a failed cluster. Please contact Customer Support if this occurs.
3751
+
**Note**: New MongoDB Databases cannot currently be created.
3768
3752
security:
3769
3753
- personalAccessToken: []
3770
3754
- oauth:
@@ -3807,8 +3791,8 @@ paths:
3807
3791
x-linode-grant: read_only
3808
3792
description: |
3809
3793
Display the root username and password for an accessible Managed MongoDB Database.
3810
-
3811
3794
The Database must have an `active` status to perform this command.
3795
+
**Note**: New MongoDB Databases cannot currently be created.
3812
3796
security:
3813
3797
- personalAccessToken: []
3814
3798
- oauth:
@@ -3851,14 +3835,11 @@ paths:
3851
3835
x-linode-grant: read_write
3852
3836
description: |
3853
3837
Reset the root password for a Managed MongoDB Database.
3854
-
3855
3838
Requires `read_write` access to the Database.
3856
-
3857
3839
A new root password is randomly generated and accessible with the **Managed MongoDB Database Credentials View** ([GET /databases/mongodb/instances/{instanceId}/credentials](/docs/api/databases/#managed-mongodb-database-credentials-view)) command.
3858
-
3859
3840
Only unrestricted Users can access this command, and have access regardless of the acting token's OAuth scopes.
3860
-
3861
3841
**Note**: Note that it may take several seconds for credentials to reset.
3842
+
**Note**: New MongoDB Databases cannot currently be created.
3862
3843
security:
3863
3844
- personalAccessToken: []
3864
3845
- oauth:
@@ -3901,8 +3882,8 @@ paths:
3901
3882
x-linode-grant: read_only
3902
3883
description: |
3903
3884
Display the SSL CA certificate for an accessible Managed MongoDB Database.
3904
-
3905
3885
The Database must have an `active` status to perform this command.
3886
+
**Note**: New MongoDB Databases cannot currently be created.
3906
3887
security:
3907
3888
- personalAccessToken: []
3908
3889
- oauth:
@@ -3945,16 +3926,12 @@ paths:
3945
3926
x-linode-grant: read_write
3946
3927
description: |
3947
3928
Apply security patches and updates to the underlying operating system of the Managed MongoDB Database. This function runs during regular maintenance windows, which are configurable with the **Managed MongoDB Database Update** ([PUT /databases/mongodb/instances/{instanceId}](/docs/api/databases/#managed-mongodb-database-update)) command.
3948
-
3949
3929
Requires `read_write` access to the Database.
3950
-
3951
3930
The Database must have an `active` status to perform this command.
3952
-
3953
3931
**Note**
3954
-
3955
3932
* If your database cluster is configured with a single node, you will experience downtime during this maintenance. Consider upgrading to a high availability plan to avoid any downtime due to maintenance.
3956
-
3957
3933
* **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.
3934
+
**Note**: New MongoDB Databases cannot currently be created.
0 commit comments