-
Notifications
You must be signed in to change notification settings - Fork 102
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
Adds Agent Pool to OAuth Client API #841
Adds Agent Pool to OAuth Client API #841
Conversation
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.
Looks good
@@ -95,6 +95,8 @@ type OAuthClient struct { | |||
// Relations | |||
Organization *Organization `jsonapi:"relation,organization"` | |||
OAuthTokens []*OAuthToken `jsonapi:"relation,oauth-tokens"` | |||
AgentPool *AgentPool `jsonapi:"relation,agent-pool"` |
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.
It appears that you've also added the inverse relationship to the API (each agent pool has_many oauth-clients). What do you think about adding include_data = false
to that new relationship in the API? Is there a good reason to serialize all of the oauth-clients associated with an agent pool?
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.
Agreed, added those changes https://github.com/hashicorp/atlas/pull/18747
} | ||
|
||
t.Run("with valid agent pool external id", func(t *testing.T) { | ||
t.Skip() |
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.
Some comments here would be appropriate
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.
Thanks for walking me through your changes over the zoom meeting!
Reminder to the contributor that merged this PR: if your changes have added important functionality or fixed a relevant bug, open a follow-up PR to update CHANGELOG.md with a note on your changes. |
Description
Currently, Private VCS support is enabled in TFC behind feature flag. This PR include changes to add API support for Private VCS by enabling creation of OAuth Client when AgentPoolID is set (as an optional param).
Testing plan
Output from tests
Including output from tests may require access to a TFE instance. Ignore this section if you have no environment to test against.