-
-
Notifications
You must be signed in to change notification settings - Fork 149
Conversation
@alexkappa do you think this is something that can be accepted soon? |
Hi Anton, I was in the middle of testing this branch yesterday but other things took away my attention. The changes look good. If tests pass I’ll merge it in |
Hey Alex, no problem! Thank you! I've run tests locally, all relevant tests passed, there were a few that failed but they're failing for me on the master branch as well. Here's the entire output just in case it will be helpful:
|
scopes = [ "email", "profile", "read_user", "follow", "public_repo", "repo", "repo_deployment", "repo_status", | ||
"delete_repo", "notifications", "gist", "read_repo_hook", "write_repo_hook", "admin_repo_hook", | ||
"read_org", "admin_org", "read_public_key", "write_public_key", "admin_public_key", "write_org" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We wouldn't necessarily need to test all scopes each time.
Tests are good, Anton. Custom domains will fail if your account is on the free tier. The rest are on how the default connection in my tenant is configured. Thank you very much! |
@alexkappa awesome, thank you! Will it be possible to cut a new release so we can start using it? |
Of course Anton. I've pinged hashicorp to cut a release. I'll push a tag here as well right away |
Community Note
Changes proposed in this pull request:
connection
resource in order to support GitHub ConnectionOutput from acceptance testing: