Seguridad de private keys para deployment DialogFlow #915
Conversation
This file contains 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
DialogFlow now allows not to push private keys to repo, instead the user can add an environment variable GOOGLE_KEY_JSON to read them from there
|
excelente graicas |
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.
Permite al usuario crear una variable de entorno GOOGLE_KEY_JSON con sus keys de Google para usar DialogFlowCX sin tener que pushear el archivo google-key.json
Que tipo de Pull Request es?
Descripción
Cambio en el archivo de DialogFlowCx dentro de contexts chequeando si existe el archivo pusheado de google keys y si no esta en el directorio utiliza la variable de entorno