Skip to content
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

Update croud.md #86

Merged
merged 2 commits into from
Aug 14, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 1 addition & 3 deletions docs/howtos/add-users.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,7 @@
# Add Users

This is a quick guide on how to add users to organizations and how to manage
their privileges. This information can also be found in the CrateDB Cloud
Console {ref}`Overview <console-overview>`, but is presented here separately
for ease of use.
their privileges.

In CrateDB Cloud, you can add team members to your organizations. In order to
add a user, they must first have signed up for CrateDB Cloud. Once they have
Expand Down
6 changes: 0 additions & 6 deletions docs/howtos/delete-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,6 @@ through Microsoft Azure, the other is for a cluster created through AWS.
For Azure, there are in turn two methods: via the CrateDB Cloud Console
and through the Azure Portal. Each are outlined in the Azure section.

Although the {ref}`general documentation <console-overview>`
for the CrateDB Cloud Console explains how you can delete a cluster
specifically within the Console, this tutorial provides a step-by-step
guide for *all* methods of deleting a CrateDB Cloud cluster. This is to
make the process more transparent and easier to find and use.

:::{Warning}
All cluster data will be lost on deletion. This action cannot be undone.
:::
Expand Down
3 changes: 0 additions & 3 deletions docs/howtos/restore-backups.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,6 @@ how one can use such snapshots to restore data. A more detailed
technical discussion of how CrateDB handles snapshots can be found in
the CrateDB documentation about {ref}`snapshots. <crate-reference:snapshot-restore>`

You may also want to read the full Cloud reference documentation on
{ref}`backups. <overview-cluster-backups>`

(snapshot-backup)=
## CrateDB Cloud's backup policy

Expand Down
11 changes: 1 addition & 10 deletions docs/reference/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,6 @@ Cloud also supports a CLI for interacting with the service, we assume
use of the Console by default. Only the Console allows deployment of a
{ref}`cluster <gloss-cluster>`.

For information on how to use specific elements of the Console, refer to
the {ref}`Console overview <console-overview>`.

(gloss-consumer)=
## Consumer

Expand Down Expand Up @@ -301,10 +298,6 @@ In CrateDB Cloud, there are two distinct system
{ref}`explanation <system-user>` in the
CrateDB Cloud reference.

:::{note}
See also {ref}`Audit Log <overview-org-audit>`
:::

(gloss-tier)=
## Tier

Expand Down Expand Up @@ -352,9 +345,7 @@ the versioning sequence, e.g. the 3 in 'version 5.3.4'.
A patch version of CrateDB is a release that includes bug fixes and
smaller quality of life improvements compared to the previous such
version. It is indicated by the third numeral in the versioning
sequence, e.g. the 4 in 'version 5.3.4'. All available upgrades are
visible in the {ref}`Manage Tab <overview-cluster-manage>` of the
cluster detailed view.
sequence, e.g. the 4 in 'version 5.3.4'.

:::{note}
See also: {ref}`CrateDB Release Notes <crate-reference:release_notes>`
Expand Down
Loading
Loading