-
Notifications
You must be signed in to change notification settings - Fork 765
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
Missing GitHub repository data source attributes #778
Missing GitHub repository data source attributes #778
Conversation
@jcudit could you unlock the workflow run so i can make sure that checks pass? |
@jcudit @anGie44 @patrickmarabeas @tracypholmes @ryndaniels @radeksimko @martinssipenko checks pass, we good to move forward on this? |
…a-source-attributes
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 these fixes!
Looks like another PR has introduced a vendoring conflict. Will merge this as-is and follow up with 3a71e80 to get CI passing. |
* has_projects * description default * Other attributes * Test on name
* has_projects * description default * Other attributes * Test on name
Greetings!
I've found in one of my projects that the Data Source for GitHub repositories continually needs to be refreshed, for example:
As you can see in the output, the following attributes are causing a refresh to be made:
name
description
has_projects
homepage_url
pages
Upon diving into these I made the following fixes:
name
: Should bename
from the API, not the calculatedname
/full_name
setting.description
is set to null when unset from the APIhas_projects
: Was missing fromdataSourceGithubRepositoryRead(...)
homepage_url
: Defaults to an empty string when unset from the APIpages
: Should be initialized to an empty list instead of simply being excludedI also wrote some tests around this, but let me know if I should add some more. Here's the final output of running
TestAccGithubRepositoryDataSource
locally:Let me know what y'all think of this!
CC'ing prior authors on this data source for additional feedback:
@jcudit @anGie44 @patrickmarabeas @tracypholmes @ryndaniels @radeksimko @martinssipenko