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

Pulling out the hardcoded test user in the Github provider for #5729 #5730

Merged
merged 1 commit into from
Mar 19, 2016

Conversation

JacobASeverson
Copy link
Contributor

From now on to run the acceptance tests a GITHUB_TEST_USER environment variable will have to be set with a valid Github user.

@jen20
Copy link
Contributor

jen20 commented Mar 19, 2016

Hi @JacobASeverson! Thanks for the pull request - tentatively this looks good, but can you explain the rationale behind this change? Thanks!

@JacobASeverson
Copy link
Contributor Author

Howdy! Sure - this is in response to what we discussed after the Github provider got merged per #5194. For the Github's acceptance tests I had hardcoded a user (TerraformDummyUser). While it is a dummy account and fine if other people run tests with it, we figured it would be better to provide a test user through an environment variable instead.

@jen20
Copy link
Contributor

jen20 commented Mar 19, 2016

Ah yes I see the discussion now, that makes sense. Do we need to replace our usage of @TerraformDummyUser in the nightly tests, or is it something you are happy for us to continue using?

@JacobASeverson
Copy link
Contributor Author

Nope, you can go ahead and keep using that account.

jen20 added a commit that referenced this pull request Mar 19, 2016
Pull out the hardcoded test user in the Github provider for #5729
@jen20 jen20 merged commit b952336 into hashicorp:master Mar 19, 2016
@jen20
Copy link
Contributor

jen20 commented Mar 19, 2016

Thanks - I'll update the nightly acceptance test scripts now.

@JacobASeverson
Copy link
Contributor Author

Cool, thanks!

@JacobASeverson JacobASeverson deleted the test_user branch March 19, 2016 17:03
@ghost
Copy link

ghost commented Apr 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants