-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
feat: Add GitLab support to report_build_status and build_status_config for aws_codebuild_project #36942
feat: Add GitLab support to report_build_status and build_status_config for aws_codebuild_project #36942
Conversation
Community NoteVoting for Prioritization
For Submitters
|
2bfcaf0
to
ca325da
Compare
…ig for aws_codebuild_project
ca325da
to
16e1fa4
Compare
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.
LGTM 🚀.
@acwwat Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.46.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This PR is to add GitLab and GitLab Self Managed support to the
report_build_status
andbuild_status_config
arguments in theaws_codebuild_project
resource. The expansion code apparently has code logic to detect the build type to determine whether these arguments/config blocks should be added. Personally I think it should be deferred to the API to determine that, but to fix the issue quickly I just follow suit for now.Relations
Closes #36937
References
Referred to ProjectSource for specs and documentation wordings. Also cross-checked the availability of options in the AWS Management Console - note that
git_submodules_config
is grayed out (and thus not supported) for GitLab source types.Output from Acceptance Testing
Note: Unfortunately I don't really have the right setup to test GitHub and BitBucket source types, so I can't really test them. I also don't have GitLab so I can't write new tests for it either even when I wanted to. If any maintainer can facilitate adding a test cases for GitLab source types, that's be greatly appreciated.