Update profiles.yml - #292
Open
MichaelTiemannOSC wants to merge 1 commit into
Open
Conversation
There are a number of Data Commons-specific parameters and secrets defined in the `credentials.env` file. The example file now shows how these parameters can be accessed using the env_var functionality of YAML files. This has the benefit that when a user is managing a number of dbt projects over a period of time, they won't have to update things like the `jwt_token` several times every few days (which gets old quickly). It has the nice side effect that the `profiles.yml` file no longer contains any secrets. Signed-off-by: Michael Tiemann <72577720+MichaelTiemannOSC@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are a number of Data Commons-specific parameters and secrets defined in the
credentials.envfile. The example file now shows how these parameters can be accessed using the env_var functionality of YAML files. This has the benefit that when a user is managing a number of dbt projects over a period of time, they won't have to update things like thejwt_tokenseveral times every few days (which gets old quickly). It has the nice side effect that theprofiles.ymlfile no longer contains any secrets.