-
Notifications
You must be signed in to change notification settings - Fork 741
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
Auth changes for vNext #987
Conversation
github/provider_utils.go
Outdated
// TODO(kfcampbell): this is a problem. how are we going to know it's an organization | ||
// in acceptance tests? | ||
// ideas: | ||
// - we could perform a lookup online to determine the type |
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.
I like this option most given we cache and reuse the result as aggressively as possible. Debug logs suggest we currently resolve an owner to an organization multiple times.
…e provider config
Will this address #977? |
👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the |
@kfcampbell if this is still valid then can you update the title to reference vNEXT to align with your new major version strategy? I understand that the branch name would look awkward but the title is misleading as there is already a v5. |
I hope that this feature will be available in 2023. 🥲 |
Done!
I apologize for the slow rate of our feature development here. If you'd like to take this branch and run with it, please feel free! |
👋 Hey Friends, this pull request has been automatically marked as |
Part of #980.
TODO:
GITHUB_TEST_ORGANIZATION
?skipUnlessMode
does the right thing with organization, user, and anonymous testsGET /orgs/kfcampbell HTTP/1.1
in the testsThis WIP PR aims to:
Note that there is another small behavior change: I doubt anyone is using this, and I don't think it's particularly good practice, but I believe it used to be possible to run actions on behalf of both an organization and an individual account, using the same token, in the same terraform file. After this v5.0.0 change is released, this will no longer be true, and setting different owners for a token will require different provider configuration. This change is intentional and (I think) a good thing.