Lucas Segers
10/28/2024, 4:47 PMuser
10/28/2024, 4:48 PMsecrets
in the config database [Airbyte Databases Data Catalog](https://docs.airbyte.com/understanding-airbyte/database-data-catalog#config-database). 3. Secrets are associated with workspaces. Each secret coordinate (the identifier for a secret) contains the workspace ID, which allows operators to understand what workspace a secret belongs to [Operational Details](https://docs.airbyte.com/understanding-airbyte/secrets#operational-details). 4. When configuration is updated, Airbyte increments a secret coordinate's version while preserving the prefix. This means you can potentially track changes to secrets over time [Operational Details](https://docs.airbyte.com/understanding-airbyte/secrets#operational-details). 5. It's important to note that Airbyte aims to keep secrets secure by not exposing them directly. The documentation states that secrets "must not be returned by the api" and "must not be printed in logs" [Understanding Airbyte Secrets](https://docs.airbyte.com/understanding-airbyte/secrets). Given this information, while you can't directly query which secrets are used by a specific source, you might be able to infer some information based on the workspace ID and the naming conventions of the secret coordinates. However, for security reasons, Airbyte intentionally limits direct access to secret information. If you need more specific information about secrets used by your sources, you might need to consult with your Airbyte administrator or refer to your source configurations, keeping in mind that the actual secret values should not be exposed.Lucas Segers
10/28/2024, 4:52 PMuser
10/28/2024, 4:52 PMairbyte-db
to store various configuration and operational data. The actor
table in this database is indeed one of the important tables that stores information about source and destination connectors. According to the [Understanding the core components: airbyte-db
> Databases and Tables](https://github.com/airbytehq/airbyte/discussions/33809) discussion, the actor
table is part of the configs
database schema. If you're trying to access or query this table, you can do so by connecting to the Airbyte database. The default method to access the database is described in the [Accessing the default database located in docker airbyte-db](https://docs.airbyte.com/operator-guides/configuring-airbyte-db#accessing-the-default-database-located-in-docker-airbyte-db) documentation: docker exec -ti airbyte-db psql -U docker -d airbyte
Once connected, you could query the actor
table to find the configuration information you're looking for. However, please note that accessing and modifying database contents directly should be done with caution, as it might affect the functioning of your Airbyte instance. If you're looking for specific information about secrets or configurations for a particular source, it might be more appropriate to use Airbyte's user interface or API to manage these settings. The exact location and format of secrets can vary depending on the specific source connector you're using.