Skip to content

production label #498

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.

Sign up for GitHub

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

Merged
merged 8 commits into from
Oct 22, 2024
Merged

production label #498

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
72139eb
production label
fiquick Oct 17, 2024
6f28f0a
production info
fiquick Oct 20, 2024
242afa9
remove image
fiquick Oct 20, 2024
32b937f
Update modules/ROOT/pages/managing-instances/instance-actions.adoc
fiquick Oct 22, 2024
301183c
Update modules/ROOT/pages/managing-instances/instance-actions.adoc
fiquick Oct 22, 2024
94af800
Update modules/ROOT/pages/managing-instances/instance-actions.adoc
fiquick Oct 22, 2024
09ee723
Update modules/ROOT/pages/managing-instances/instance-actions.adoc
fiquick Oct 22, 2024
5c4abf2
update
fiquick Oct 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions modules/ROOT/pages/managing-instances/instance-actions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,3 +187,17 @@ Type the exact name of the instance (as instructed) to confirm your decision, an
====
There is no way to recover data from a deleted Aura instance.
====

== Mark an instance as `production`

label:AuraDB-Virtual-Dedicated-Cloud[]
label:AuraDB-Business-Critical[]

Admins can mark a database instance as `production` in AuraDB Virtual Dedicated Cloud and AuraDB Business Critical.

When Neo4j updates Aura Database versions, instances marked as `production` are last to have the Aura Database version updated.
Because updates are applied to these database instances after other database instances receive updates, you can monitor any potential impact on less critical instances first.

After marking the instance as `production` the label is applied immediately, and all instance actions (such as pause or clone) are temporarily unavailable while the instance is set to `production` in the Neo4j backend.

Use the more menu (three dots) on the instance card to mark it as `production`.