Meta tags:
description=The credentials in a deployed Rill Cloud projects can be managed on the Settings page or via the CLI. If you have yet to deploy your credentials, please follow the steps in our deploy credentials page.;

Headings (most frequently used words):

and, credentials, rill, variables, env, environmental, cloud, via, the, in, modifying, settings, page, pushing, pulling, to, from, cli, adding, editing, importing, file, push, pull, naming, schema,

Text of the page (most frequently used words):
rill (39), credentials (32), the (25), env (24), and (21), cloud (17), your (17), #variables (15), project (14), you (13), file (12), pull (10), use (9), will (9), push (8), cli (8), can (8), via (7), this (7), from (6), #environmental (6), settings (6), for (6), have (6), that (6), naming (5), page (5), please (5), local (5), deployed (5), dsn (4), google_application_credentials (4), connector (4), run (4), been (4), are (4), locally (4), overriding (4), developer (4), files (4), user (4), users (3), github (3), projects (3), convention (3), configured (3), there (3), with (3), our (3), these (3), git (3), sensitive (3), hidden (3), tokens (3), time (3), dashboards (3), policy (2), service (2), schema (2), pushing (2), pulling (2), adding (2), editing (2), importing (2), modifying (2), integration (2), password (2), clickhouse (2), azure_storage_sas_token (2), azure_storage_connection_string (2), azure_storage_key (2), azure_storage_account (2), aws_secret_access_key (2), aws_access_key_id (2), environment (2), variable (2), property (2), source (2), name (2), may (2), syntax (2), format (2), like (2), driver (2), see (2), below (2), any (2), need (2), contact (2), automatically (2), updated (2), added (2), manually (2), retrieve (2), other (2), they (2), defined (2), commit (2), information (2), set (2), them (2), managed (2), visible (2), deploy (2), administration (2), access (2), reports (2), 2026, data, inc, contributing, community, terms, privacy, next, previous, clickhouse_dsn, clickhouse_database, database, clickhouse_ssl, ssl, clickhouse_password, clickhouse_username, username, clickhouse_port, port, clickhouse_host, host, snowflake_password, snowflake_dsn, snowflake, big, query, azure, aws, gcp_secret_access_key, secret, gcp_access_key_id, key_id, gcs, older, still, supported, backwards, compatibility, druid, connector_name, legacy, standardized, generic, shared, across, connectors, providers, standard, names, without, prefix, while, specific, each, its, required, properties, questions, specifics, driver_property, note, when, match, key, result, unexpected, behavior, using, different, override, existing, project_name, benefit, architecture, pulled, easier, reuse, instead, having, reconfigure, root, directory, latest, after, cloning, repository, credential, has, already, warn, about, attempt, new, value, because, impact, also, able, specified, admin, update, contexts, rill_project_home, never, good, idea, goes, against, security, best, practices, similar, don, want, publicly, configuration, thus, potentially, accessible, others, recommended, directly, then, optionally, necessary, yaml, avoid, committing, prefer, done, running, default, not, finder, window, order, view, enable, show, keyboard, shortcut, command, shift, find, once, modified, needed, upon, deployment, populated, contents, seen, add, get, started, yet, follow, steps, home, release, notes, roles, permissions, groups, management, organization, alerts, exports, scheduled, public, shareable, urls, bookmarks, sharing, filters, comparisons, series, filter, canvas, pivot, flat, tables, dimension, detail, multiple, measure, leaderboard, explore, mcp, server, chat, search, blog, rest, api, url, parameters, iso, 8601, reference, guide, developers, skip, main, content,

Text of the page (random words):
environmental variables and credentials in rill cloud rill skip to main content developers guide reference project files time syntax rill iso 8601 url parameters cli rest api contact us blog github search rill cloud ai ai chat rill mcp server dashboards explore dashboards multiple measure leaderboard time dimension detail pivot and flat tables canvas dashboards time series filter filters comparisons bookmarks sharing public shareable urls reports exports scheduled reports alerts administration organization settings project settings github integration variables and credentials user access user management user groups roles and permissions access tokens user tokens service tokens release notes home administration project settings variables and credentials on this page environmental variables and credentials in rill cloud the credentials in a deployed rill cloud projects can be managed on the settings page or via the cli if you have yet to deploy your credentials please follow the steps in our deploy credentials page modifying variables and credentials via the settings page upon deployment via rill developer if you have populated your env file the contents will be visible as seen below if there are no environmental variables defined please run rill env push from your local cli and rill will automatically push the credentials in your project s env file to rill cloud if you d like to manually add the credentials please see our naming convention to get started adding and editing environmental variables importing a env file once your environmental variables are added to rill cloud they can be modified as needed can t find the env file by default the hidden files will not be visible in the finder window in order to view hidden files you will need to enable show hidden files keyboard shortcut command shift pushing and pulling credentials to from rill cloud via the cli if you d prefer to use the cli to managed your credentials this can be done by running the rill env pull to pull your deployed rill cloud project s variables locally or rill env push to updated rill cloud project s variables avoid committing sensitive information to git it s never a good idea to commit sensitive information to git and goes against security best practices similar to credentials if there are sensitive variables that you don t want to commit publicly to your rill yaml configuration file and thus potentially accessible by others it s recommended to set them in your env file directly and or use rill env set via the cli and then optionally push pull them as necessary rill env push as a project admin you can run rill env push from your local cli that will update your rill project with the contexts of your rill_project_home env file rill cloud will use the specified credentials and variables in this env file for the deployed project other users will also be able to use rill env pull to retrieve these defined credentials for local use with rill developer overriding cloud credentials if a credential and or variable has already been configured in rill cloud rill will warn you about overriding if you attempt to push a new value in your env file this is because overriding credentials can impact your deployed project and or other users if they pull these credentials locally rill env pull for projects that have been deployed to rill cloud an added benefit of our rill developer cloud architecture is that credentials that have been configured can be pulled locally for easier reuse instead of having to manually reconfigure these credentials in rill developer to do this you can run rill env pull from your project s root directory to retrieve the latest credentials after cloning the project s git repository to your local environment rill env pull updated env file with cloud credentials from project project_name overriding local credentials please note when you run rill env pull rill will automatically override any existing credentials or variables that have been configured in your project s env file if there is a match in the key name this may result in unexpected behavior if you are using different credentials locally credentials naming schema connector credentials use a standardized naming convention generic credentials shared across connectors like cloud providers use standard names without a driver prefix while driver specific credentials use the driver_property format please see below for each source and its required properties if you have any questions or need specifics contact us legacy naming convention older projects may use the connector connector_name property syntax e g connector druid dsn connector clickhouse dsn this format is still supported for backwards compatibility source name property environment variable gcs google_application_credentials google_application_credentials key_id gcp_access_key_id secret gcp_secret_access_key aws s3 aws_access_key_id aws_access_key_id aws_secret_access_key aws_secret_access_key azure azure_storage_account azure_storage_account azure_storage_key azure_storage_key azure_storage_connection_string azure_storage_connection_string azure_storage_sas_token azure_storage_sas_token big query google_application_credentials google_application_credentials snowflake dsn snowflake_dsn password snowflake_password clickhouse host clickhouse_host port clickhouse_port username clickhouse_username password clickhouse_password ssl clickhouse_ssl database clickhouse_database dsn clickhouse_dsn previous github integration next users modifying variables and credentials via the settings page adding and editing environmental variables importing a env file pushing and pulling credentials to from rill cloud via the cli rill env push rill env pull credentials naming schema 2026 rill data inc privacy policy terms of service community policy contributing