Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Developer account for CI pipeline #4

Open
florish opened this issue Nov 14, 2015 · 0 comments
Open

Developer account for CI pipeline #4

florish opened this issue Nov 14, 2015 · 0 comments

Comments

@florish
Copy link
Contributor

florish commented Nov 14, 2015

We currently cannot make CI builds pass, as we do not have a Buckaroo developer account for which we can safely put credentials on a CI server.

To be sure: we don't need these credentials for doing actual transaction requests on the CI server, the vcr gem can handle this nicely for us. The reason we need them is that recorded VCR responses have a response signature baked in, which can only be verified with the same BUCKAROO_CLIENT_SECRET that was used when the request was recorded. Recording with VCR only makes sense with a developer account, as we do not want to store a real Buckaroo user's SECRET on a CI server for obvious reasons.

Unfortunately, requesting a developer account is a manual process at Buckaroo, which involves signatures on paper and sending stuff by snail mail, which is why we haven't done this so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant