mirror of
https://github.com/zitadel/zitadel.git
synced 2025-04-16 11:51:30 +00:00
2243306ef6
# Which Problems Are Solved Adds the possibility to mirror an existing database to a new one. For that a new command was added `zitadel mirror`. Including it's subcommands for a more fine grained mirror of the data. Sub commands: * `zitadel mirror eventstore`: copies only events and their unique constraints * `zitadel mirror system`: mirrors the data of the `system`-schema * `zitadel mirror projections`: runs all projections * `zitadel mirror auth`: copies auth requests * `zitadel mirror verify`: counts the amount of rows in the source and destination database and prints the diff. The command requires one of the following flags: * `--system`: copies all instances of the system * `--instance <instance-id>`, `--instance <comma separated list of instance ids>`: copies only the defined instances The command is save to execute multiple times by adding the `--replace`-flag. This replaces currently existing data except of the `events`-table # Additional Changes A `--for-mirror`-flag was added to `zitadel setup` to prepare the new database. The flag skips the creation of the first instances and initial run of projections. It is now possible to skip the creation of the first instance during setup by setting `FirstInstance.Skip` to true in the steps configuration. # Additional info It is currently not possible to merge multiple databases. See https://github.com/zitadel/zitadel/issues/7964 for more details. It is currently not possible to use files. See https://github.com/zitadel/zitadel/issues/7966 for more information. closes https://github.com/zitadel/zitadel/issues/7586 closes https://github.com/zitadel/zitadel/issues/7486 ### Definition of Ready - [x] I am happy with the code - [x] Short description of the feature/issue is added in the pr description - [x] PR is linked to the corresponding user story - [x] Acceptance criteria are met - [x] All open todos and follow ups are defined in a new ticket and justified - [x] Deviations from the acceptance criteria and design are agreed with the PO and documented. - [x] No debug or dead code - [x] My code has no repetitions - [x] Critical parts are tested automatically - [ ] Where possible E2E tests are implemented - [x] Documentation/examples are up-to-date - [x] All non-functional requirements are met - [x] Functionality of the acceptance criteria is checked manually on the dev system. --------- Co-authored-by: Livio Spring <livio.a@gmail.com>
43 lines
1.5 KiB
Markdown
43 lines
1.5 KiB
Markdown
---
|
|
title: Settings
|
|
---
|
|
|
|
Manage your team, email subscriptions, and billing information on the [Settings](https://zitadel.com/admin/settings) page.
|
|
|
|
## Team name
|
|
|
|
Change your ZITADEL Cloud team name by entering a new name.
|
|
Confirm the changes by clicking the Change button.
|
|
|
|
## Notifications and newsletters
|
|
|
|
You can subscribe and unsubscribe to notifications and newsletters:
|
|
|
|
- Onboarding: Welcome information for new users
|
|
- Newsletter: Regular newsletter on ZITADEL
|
|
- Product News: Receive product updates
|
|
- Security: Receive notifications related to security issues
|
|
|
|
:::info Technical Advisories
|
|
If you want to stay up to date on our technical advisories, we recommend [subscribing here to the mailing list](/docs/support/technical_advisory#subscribe-to-our-mailing-list).
|
|
|
|
Technical advisories are notices that report major issues with ZITADEL Self-Hosted or the ZITADEL Cloud platform that could potentially impact security or stability in production environments.
|
|
:::
|
|
|
|
You can also manage your subscriptions by clicking the unsubscribe link in the emails.
|
|
|
|
:::info Mandatory Information
|
|
We are required to inform you about changes to the terms of service or based on regulatory requirements. You can't unsubscribe to these notifications.
|
|
:::
|
|
|
|
## Delete team
|
|
|
|
Permanently delete your ZITADEL Cloud account.
|
|
This will delete your team and delete all associated information.
|
|
|
|
Click **Delete Account** and confirm the next step.
|
|
|
|
## Update billing information
|
|
|
|
Refer to the [billing guide](./billing.md).
|