mirror of
https://github.com/letic/terraform-provider-google.git
synced 2024-07-01 07:42:40 +00:00
Use differentiated issue templates.
I largely stole these from github.com/terraform-providers/terraform-provider-aws, but with a few changes: * I called out how we assign users to issues, to make it more transparent to users. * I added a "success story" issue that will be automatically closed and labeled, to keep track of those stories. * I added a `[issue-type:TYPE]` string to each, so hashibot can detect and act on them.
This commit is contained in:
Paddy
parent
96b17536b9
commit
4678bee194
77
.github/ISSUE_TEMPLATE/bug.md
vendored
Normal file
77
.github/ISSUE_TEMPLATE/bug.md
vendored
Normal file
|
|
@ -0,0 +1,77 @@
|
|||
---
|
||||
name: Bug
|
||||
about: For when something is there, but doesn't work how it should.
|
||||
|
||||
---
|
||||
|
||||
<!--- Please leave this line, it helps our automation: [issue-type:bug-report] --->
|
||||
<!--- Please keep this note for the community --->
|
||||
|
||||
### Community Note
|
||||
|
||||
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
|
||||
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
|
||||
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
|
||||
* If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
|
||||
|
||||
<!--- Thank you for keeping this note for the community --->
|
||||
|
||||
### Terraform Version
|
||||
|
||||
<!--- Please run `terraform -v` to show the Terraform core version and provider version(s). If you are not running the latest version of Terraform or the provider, please upgrade because your issue may have already been fixed. [Terraform documentation on provider versioning](https://www.terraform.io/docs/configuration/providers.html#provider-versions). --->
|
||||
|
||||
### Affected Resource(s)
|
||||
|
||||
<!--- Please list the affected resources and data sources. --->
|
||||
|
||||
* google_XXXXX
|
||||
|
||||
### Terraform Configuration Files
|
||||
|
||||
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
|
||||
|
||||
```tf
|
||||
# Copy-paste your Terraform configurations here - for large Terraform configs,
|
||||
# please use a service like Dropbox and share a link to the ZIP file. For
|
||||
# security, you can also encrypt the files using our GPG public key: https://www.hashicorp.com/security
|
||||
```
|
||||
|
||||
### Debug Output
|
||||
|
||||
<!---
|
||||
Please provide a link to a GitHub Gist containing the complete debug output. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
|
||||
|
||||
To obtain the debug output, see the [Terraform documentation on debugging](https://www.terraform.io/docs/internals/debugging.html).
|
||||
--->
|
||||
|
||||
### Panic Output
|
||||
|
||||
<!--- If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the `crash.log`. --->
|
||||
|
||||
### Expected Behavior
|
||||
|
||||
<!--- What should have happened? --->
|
||||
|
||||
### Actual Behavior
|
||||
|
||||
<!--- What actually happened? --->
|
||||
|
||||
### Steps to Reproduce
|
||||
|
||||
<!--- Please list the steps required to reproduce the issue. --->
|
||||
|
||||
1. `terraform apply`
|
||||
|
||||
### Important Factoids
|
||||
|
||||
<!--- Are there anything atypical about your accounts that we should know? For example: authenticating as a user instead of a service account? --->
|
||||
|
||||
### References
|
||||
|
||||
<!---
|
||||
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
|
||||
|
||||
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
|
||||
--->
|
||||
|
||||
* #0000
|
||||
77
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
77
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
|
|
@ -0,0 +1,77 @@
|
|||
---
|
||||
name: Bug report
|
||||
about: For when something is there, but doesn't work how it should.
|
||||
|
||||
---
|
||||
|
||||
<!--- Please leave this line, it helps our automation: [issue-type:bug-report] --->
|
||||
<!--- Please keep this note for the community --->
|
||||
|
||||
### Community Note
|
||||
|
||||
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
|
||||
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
|
||||
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
|
||||
* If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
|
||||
|
||||
<!--- Thank you for keeping this note for the community --->
|
||||
|
||||
### Terraform Version
|
||||
|
||||
<!--- Please run `terraform -v` to show the Terraform core version and provider version(s). If you are not running the latest version of Terraform or the provider, please upgrade because your issue may have already been fixed. [Terraform documentation on provider versioning](https://www.terraform.io/docs/configuration/providers.html#provider-versions). --->
|
||||
|
||||
### Affected Resource(s)
|
||||
|
||||
<!--- Please list the affected resources and data sources. --->
|
||||
|
||||
* google_XXXXX
|
||||
|
||||
### Terraform Configuration Files
|
||||
|
||||
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
|
||||
|
||||
```tf
|
||||
# Copy-paste your Terraform configurations here - for large Terraform configs,
|
||||
# please use a service like Dropbox and share a link to the ZIP file. For
|
||||
# security, you can also encrypt the files using our GPG public key: https://www.hashicorp.com/security
|
||||
```
|
||||
|
||||
### Debug Output
|
||||
|
||||
<!---
|
||||
Please provide a link to a GitHub Gist containing the complete debug output. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
|
||||
|
||||
To obtain the debug output, see the [Terraform documentation on debugging](https://www.terraform.io/docs/internals/debugging.html).
|
||||
--->
|
||||
|
||||
### Panic Output
|
||||
|
||||
<!--- If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the `crash.log`. --->
|
||||
|
||||
### Expected Behavior
|
||||
|
||||
<!--- What should have happened? --->
|
||||
|
||||
### Actual Behavior
|
||||
|
||||
<!--- What actually happened? --->
|
||||
|
||||
### Steps to Reproduce
|
||||
|
||||
<!--- Please list the steps required to reproduce the issue. --->
|
||||
|
||||
1. `terraform apply`
|
||||
|
||||
### Important Factoids
|
||||
|
||||
<!--- Are there anything atypical about your accounts that we should know? For example: authenticating as a user instead of a service account? --->
|
||||
|
||||
### References
|
||||
|
||||
<!---
|
||||
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
|
||||
|
||||
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
|
||||
--->
|
||||
|
||||
* #0000
|
||||
45
.github/ISSUE_TEMPLATE/enhancement.md
vendored
Normal file
45
.github/ISSUE_TEMPLATE/enhancement.md
vendored
Normal file
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
name: Enhancement
|
||||
about: For when something (a resource, field, etc.) is missing, but should be added.
|
||||
|
||||
---
|
||||
|
||||
<!--- Please leave this line, it helps our automation: [issue-type:enhancement] --->
|
||||
<!--- Please keep this note for the community --->
|
||||
|
||||
### Community Note
|
||||
|
||||
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
|
||||
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
|
||||
* If you are interested in working on this issue or have submitted a pull request, please leave a commentIf the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
|
||||
|
||||
<!--- Thank you for keeping this note for the community --->
|
||||
|
||||
### Description
|
||||
|
||||
<!--- Please leave a helpful description of the feature request here. Including use cases and why it would help you is a great way to convince maintainers to spend time on it. --->
|
||||
|
||||
### New or Affected Resource(s)
|
||||
|
||||
<!--- Please list the new or affected resources and data sources. --->
|
||||
|
||||
* google_XXXXX
|
||||
|
||||
### Potential Terraform Configuration
|
||||
|
||||
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
|
||||
|
||||
```tf
|
||||
# Propose what you think the configuration to take advantage of this feature should look like.
|
||||
# We may not use it verbatim, but it's helpful in understanding your intent.
|
||||
```
|
||||
|
||||
### References
|
||||
|
||||
<!---
|
||||
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
|
||||
|
||||
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation?
|
||||
--->
|
||||
|
||||
* #0000
|
||||
44
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
44
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
|
|
@ -0,0 +1,44 @@
|
|||
---
|
||||
name: Feature request
|
||||
about: For when something (a resource, field, etc.) is missing, but should be added.
|
||||
|
||||
---
|
||||
|
||||
<!--- Please keep this note for the community --->
|
||||
|
||||
### Community Note
|
||||
|
||||
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
|
||||
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
|
||||
* If you are interested in working on this issue or have submitted a pull request, please leave a commentIf the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
|
||||
|
||||
<!--- Thank you for keeping this note for the community --->
|
||||
|
||||
### Description
|
||||
|
||||
<!--- Please leave a helpful description of the feature request here. Including use cases and why it would help you is a great way to convince maintainers to spend time on it. --->
|
||||
|
||||
### New or Affected Resource(s)
|
||||
|
||||
<!--- Please list the new or affected resources and data sources. --->
|
||||
|
||||
* google_XXXXX
|
||||
|
||||
### Potential Terraform Configuration
|
||||
|
||||
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
|
||||
|
||||
```tf
|
||||
# Propose what you think the configuration to take advantage of this feature should look like.
|
||||
# We may not use it verbatim, but it's helpful in understanding your intent.
|
||||
```
|
||||
|
||||
### References
|
||||
|
||||
<!---
|
||||
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
|
||||
|
||||
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation?
|
||||
--->
|
||||
|
||||
* #0000
|
||||
17
.github/ISSUE_TEMPLATE/question.md
vendored
Normal file
17
.github/ISSUE_TEMPLATE/question.md
vendored
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
name: Question
|
||||
about: If you have a question, please check out our community resources!
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
|
||||
Issues on GitHub are intended to be related to bugs or feature requests with provider codebase,
|
||||
so we recommend using our other community resources instead of asking here 👍.
|
||||
|
||||
---
|
||||
|
||||
If you have a support request or question please submit them to one of these resources:
|
||||
|
||||
* [Terraform community resources](https://www.terraform.io/docs/extend/community/index.html)
|
||||
* [HashiCorp support](https://support.hashicorp.com) (Terraform Enterprise customers)
|
||||
26
.github/ISSUE_TEMPLATE/success-story.md
vendored
Normal file
26
.github/ISSUE_TEMPLATE/success-story.md
vendored
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
name: Success story
|
||||
about: Tell us about how the provider worked out well for you and things you love
|
||||
about it.
|
||||
|
||||
---
|
||||
|
||||
<!--- Please leave this line, it helps our automation: [issue-type:success] --->
|
||||
<!---
|
||||
This is a different kind of issue, in that it's not an issue at all. It's a way for you to share
|
||||
your story of how the Google provider helped you, worked out well for your project, or
|
||||
in other ways contributed to your project's success. You're free to share as much or as
|
||||
little detail as you like--from sharing the exact config you used, to not even mentioning
|
||||
the name of the company or the project.
|
||||
|
||||
Issues posted using this template don't require maintainer work, so they'll be automatically
|
||||
closed, but will be labeled using the `success-story` label, so other users can find them,
|
||||
and can gauge what the project is useful for and how it can help them.
|
||||
--->
|
||||
|
||||
**Company**:
|
||||
**Project**:
|
||||
|
||||
## How the Google Provider Helped
|
||||
|
||||
## Things I Really Enjoyed About Using the Provider
|
||||
Loading…
Reference in New Issue
Block a user