Store and inspect your first secret
Create a disposable public secret type and site secret in TaruviBase Console, view the masked result, and remove both resources. Use a development site and never substitute a real credential.
Before you begin
Sign in to Console and select the intended organization and non-production site. You will use the site's Settings and Secrets tabs.
Anyone signed in with access to the site can currently create, change, and delete secrets, so only give site access to people you trust with them.
1. Create a secret type
- Select the site Settings tab.
- In the settings navigation, select Secret Types.
- Select Create Secret Type. If the list is empty, the equivalent button is Create Your First Secret Type.
- In Create New Secret Type, enter:
- Name:
app_config - Description:
Application configuration - Sensitivity Level: Public
- Name:
- Under Define Secret Schema, use Add Field to add:
feature_x, type Boolean;region, type String.
- Select Create Secret Type.
The sensitivity level can't be changed after creation. The new type appears under Secret Types with its sensitivity badge and field count.
2. Store a site secret
- Select the site Secrets tab.
- Select Create Secret.
- In Create New Secret, enter:
- Key:
app_config - Secret Type:
app_config - Tags (optional): leave empty for this tutorial
- Key:
- In app_config Configuration, set
feature_xto true andregiontous-east-1. - Select Create Secret.
Opening Secrets at site level creates a site-scoped secret; the dialog has
no separate scope selector. Console currently accepts letters, numbers, _,
and - in Key, which is narrower than the backend key grammar documented in
the runtime reference.
3. Inspect the result
The Secrets page shows the new key with type, masked value, and tags. Select
the app_config card or row to open its detail dialog.
Values remain masked until you select Show. Copy and Copy all values place plaintext on the clipboard, so do not use those controls for this tutorial. Confirm only that the two expected field names exist, then close the dialog.
Delete the secret
Deleting app_config removes its value from the site. TaruviBase does not retain a
recoverable value in history.
Before selecting Delete:
- Affected resource and cascade — confirm the
app_configkey on the site Secrets page. Removing a site value affects apps that use its fallback. - Reversibility — treat the deletion as irreversible.
- Authorization — anyone with access to the site can delete secrets, so confirm you are on the right site.
- Backup — this is disposable data. If you used another value, place any required backup in an approved secret store first.
- Confirmation — open the detail dialog once more and confirm the key and site scope, then choose Delete.
- Success and postcondition — in Delete Secret, select Delete, then confirm the key no longer appears after Refresh.
- Recovery — recreate the secret from an approved backup if deletion was unintended.
Delete the secret type
Deleting app_config removes its schema and sensitivity definition. It does not
restore or preserve deleted secret values.
Before selecting Delete Secret Type:
- Affected resource and cascade — return to site Settings → Secret
Types and confirm
app_config. The backend rejects deletion while a secret still uses the type; system types cannot be deleted. - Reversibility — treat removal of the definition as irreversible.
- Authorization — anyone with access to the site can delete secret types, so confirm you are on the right site.
- Backup — record the schema in an approved store if it is not disposable.
- Confirmation — use the card's delete action and verify Delete Secret
Type names
app_config. - Success and postcondition — select Delete Secret Type, then confirm it no longer appears in the list.
- Recovery — recreate the type and any required secrets from approved backups.
Next steps
- Manage secrets in TaruviBase Console for Console edit and delete workflows.
- Read secrets from an SDK for JavaScript and Python runtime reads.
- Learn scope, sensitivity, and resolution.
- Review the access model and Console disclosure controls.