-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[IND-4227] [COMPLIANCE] Update Copyright Headers (Batch 22 of 61) #45441
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
[IND-4227] [COMPLIANCE] Update Copyright Headers (Batch 22 of 61) #45441
Conversation
|
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
|
Implemented via #45517 et al. |
|
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
Hi there 👋
This PR was auto-generated as part of an internal review of repositories that are not in compliance with IBM's licensing standards.
This is batch 22 of 61 - Multiple PRs are being created to make review easier.
Repository Information
Frequently Asked Questions
Why am I getting this PR?
This pull request was created because one or more source code files were found incorrect copyright and/or license headers.More info is available in these documents - MEMO.
Old Hashicorp Copyright details can be viewed here - RFC.
How do you determine which files should get copyright headers?
Attempts are made to skip scanning autogenerated files (e.g., `go.mod`) and prose. If you find file types you feel should be excluded from future scans, please reach out to:#proj-software-copyright
I have a file or folder which should be exempted, how do I do that?
You may exempt certain files or folders from being scanned by adding a `.copywrite.hcl` config in the root of your repo. You can use the [`copywrite init`](https://go.hashi.co/copywrite) command to interactively create a config for this project.An example schema can be found below. Add a doublestar**-capable pattern to the
header_ignorelist to skip it in future scans.Additional FAQs are available at https://go.hashi.co/header-faq
Please approve and merge this PR in a timely manner to keep this source code compliant with our OSS license agreement. If you have any questions or feedback, reach out to #proj-software-copyright.
Thank you!
Powered by copywrite, made with ❤️ by @hashicorp