Encrypt fanjoula.json, decrypt on Travis CI #36 #52
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.
This patch allows the client secret for the live staging website (Google Cloud Platform) to be accessed by Travis CI for real end-to-end integration testing of the datastore.
We do this by encrypting the client secret, adding to GitHub, and decrypting it on Travis CI.
Thanks goes to this tutorial:
https://dev.to/mmphego/how-to-encrypt-multiple-files-with-travis-ci-5a15
.gitignore
Update to ignore unencrypted client secret
.travis.yml
Decrypt client secret, untar (Autogenerated with ruby gem
travis
)fanjoula.json
Revoke this client secret for live staging site
secrets.tar.enc
Add client secret