Skip to content

Commit 09c8956

Browse files
authored
Migrate to ChatOps (cloudposse#28)
1 parent 8f3c50b commit 09c8956

File tree

10 files changed

+267
-166
lines changed

10 files changed

+267
-166
lines changed

.github/CODEOWNERS

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# Use this file to define individuals or teams that are responsible for code in a repository.
2+
# Read more: <https://help.github.com/articles/about-codeowners/>
3+
#
4+
# Order is important: the last matching pattern takes the most precedence
5+
6+
# These owners will be the default owners for everything
7+
* @cloudposse/engineering @cloudposse/contributors
8+
9+
# Cloud Posse must review any changes to Makefiles
10+
**/Makefile @cloudposse/engineering
11+
**/Makefile.* @cloudposse/engineering
12+
13+
# Cloud Posse must review any changes to GitHub actions
14+
.github/* @cloudposse/engineering

.github/ISSUE_TEMPLATE/bug_report.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: 'bug'
6+
assignees: ''
7+
8+
---
9+
10+
Found a bug? Maybe our [Slack Community](https://slack.cloudposse.com) can help.
11+
12+
[![Slack Community](https://slack.cloudposse.com/badge.svg)](https://slack.cloudposse.com)
13+
14+
## Describe the Bug
15+
A clear and concise description of what the bug is.
16+
17+
## Expected Behavior
18+
A clear and concise description of what you expected to happen.
19+
20+
## Steps to Reproduce
21+
Steps to reproduce the behavior:
22+
1. Go to '...'
23+
2. Run '....'
24+
3. Enter '....'
25+
4. See error
26+
27+
## Screenshots
28+
If applicable, add screenshots or logs to help explain your problem.
29+
30+
## Environment (please complete the following information):
31+
32+
Anything that will help us triage the bug will help. Here are some ideas:
33+
- OS: [e.g. Linux, OSX, WSL, etc]
34+
- Version [e.g. 10.15]
35+
36+
## Additional Context
37+
Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
blank_issues_enabled: false
2+
3+
contact_links:
4+
5+
- name: Community Slack Team
6+
url: https://cloudposse.com/slack/
7+
about: |-
8+
Please ask and answer questions here.
9+
10+
- name: Office Hours
11+
url: https://cloudposse.com/office-hours/
12+
about: |-
13+
Join us every Wednesday for FREE Office Hours (lunch & learn).
14+
15+
- name: DevOps Accelerator Program
16+
url: https://cloudposse.com/accelerate/
17+
about: |-
18+
Own your infrastructure in record time. We build it. You drive it.
+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: 'feature request'
6+
assignees: ''
7+
8+
---
9+
10+
Have a question? Please checkout our [Slack Community](https://slack.cloudposse.com) or visit our [Slack Archive](https://archive.sweetops.com/).
11+
12+
[![Slack Community](https://slack.cloudposse.com/badge.svg)](https://slack.cloudposse.com)
13+
14+
## Describe the Feature
15+
16+
A clear and concise description of what the bug is.
17+
18+
## Expected Behavior
19+
20+
A clear and concise description of what you expected to happen.
21+
22+
## Use Case
23+
24+
Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.
25+
26+
## Describe Ideal Solution
27+
28+
A clear and concise description of what you want to happen. If you don't know, that's okay.
29+
30+
## Alternatives Considered
31+
32+
Explain what alternative solutions or features you've considered.
33+
34+
## Additional Context
35+
36+
Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question.md

Whitespace-only changes.

.github/PULL_REQUEST_TEMPLATE.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
## what
2+
* Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
3+
* Use bullet points to be concise and to the point.
4+
5+
## why
6+
* Provide the justifications for the changes (e.g. business case).
7+
* Describe why these changes were made (e.g. why do these commits fix the problem?)
8+
* Use bullet points to be concise and to the point.
9+
10+
## references
11+
* Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
12+
* Use `closes #123`, if this PR closes a GitHub issue `#123`
13+

.github/workflows/chatops.yml

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
name: chatops
2+
on:
3+
issue_comment:
4+
types: [created]
5+
6+
jobs:
7+
default:
8+
runs-on: ubuntu-latest
9+
steps:
10+
- uses: actions/checkout@v2
11+
- name: "Handle common commands"
12+
uses: cloudposse/actions/github/[email protected]
13+
with:
14+
token: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }}
15+
reaction-token: ${{ secrets.GITHUB_TOKEN }}
16+
repository: cloudposse/actions
17+
commands: rebuild-readme, terraform-fmt
18+
permission: none
19+
issue-type: pull-request
20+
21+
test:
22+
runs-on: ubuntu-latest
23+
steps:
24+
- name: "Checkout commit"
25+
uses: actions/checkout@v2
26+
- name: "Run tests"
27+
uses: cloudposse/actions/github/[email protected]
28+
with:
29+
token: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }}
30+
reaction-token: ${{ secrets.GITHUB_TOKEN }}
31+
repository: cloudposse/actions
32+
commands: test
33+
permission: none
34+
issue-type: pull-request
35+
reactions: false
36+
37+

README.md

+91-44
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,48 @@
1-
<!-- This file was automatically generated by the `build-harness`. Make all changes to `README.yaml` and run `make readme` to rebuild this file. -->
1+
<!--
2+
3+
4+
5+
6+
7+
8+
9+
10+
11+
12+
13+
14+
15+
16+
** DO NOT EDIT THIS FILE
17+
**
18+
** This file was automatically generated by the `build-harness`.
19+
** 1) Make all changes to `README.yaml`
20+
** 2) Run `make init` (you only need to do this once)
21+
** 3) Run`make readme` to rebuild this file.
22+
**
23+
** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.)
24+
**
25+
26+
27+
28+
29+
30+
31+
32+
33+
34+
35+
36+
37+
38+
39+
40+
-->
241
[![README Header][readme_header_img]][readme_header_link]
342

443
[![Cloud Posse][logo]](https://cpco.io/homepage)
544

6-
# terraform-aws-alb-ingress [![Codefresh Build Status](https://g.codefresh.io/api/badges/pipeline/cloudposse/terraform-modules%2Fterraform-aws-alb-ingress?type=cf-1)](https://g.codefresh.io/public/accounts/cloudposse/pipelines/5db79c3e041f80d14e93f012) [![Latest Release](https://img.shields.io/github/release/cloudposse/terraform-aws-alb-ingress.svg)](https://github.com/cloudposse/terraform-aws-alb-ingress/releases/latest) [![Slack Community](https://slack.cloudposse.com/badge.svg)](https://slack.cloudposse.com)
45+
# terraform-aws-alb-ingress [![Latest Release](https://img.shields.io/github/release/cloudposse/terraform-aws-alb-ingress.svg)](https://github.com/cloudposse/terraform-aws-alb-ingress/releases/latest) [![Slack Community](https://slack.cloudposse.com/badge.svg)](https://slack.cloudposse.com)
746

847

948
Terraform module to provision an HTTP style ALB ingress based on hostname and/or path.
@@ -232,42 +271,51 @@ Check out these related projects.
232271

233272
## Help
234273

235-
**Got a question?**
274+
**Got a question?** We got answers.
236275

237276
File a GitHub [issue](https://github.com/cloudposse/terraform-aws-alb-ingress/issues), send us an [email][email] or join our [Slack Community][slack].
238277

239278
[![README Commercial Support][readme_commercial_support_img]][readme_commercial_support_link]
240279

241-
## Commercial Support
242-
243-
Work directly with our team of DevOps experts via email, slack, and video conferencing.
280+
## DevOps Accelerator for Startups
244281

245-
We provide [*commercial support*][commercial_support] for all of our [Open Source][github] projects. As a *Dedicated Support* customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.
246282

247-
[![E-Mail](https://img.shields.io/badge/[email protected])][email]
283+
We are a [**DevOps Accelerator**][commercial_support]. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
248284

249-
- **Questions.** We'll use a Shared Slack channel between your team and ours.
250-
- **Troubleshooting.** We'll help you triage why things aren't working.
251-
- **Code Reviews.** We'll review your Pull Requests and provide constructive feedback.
252-
- **Bug Fixes.** We'll rapidly work to fix any bugs in our projects.
253-
- **Build New Terraform Modules.** We'll [develop original modules][module_development] to provision infrastructure.
254-
- **Cloud Architecture.** We'll assist with your cloud strategy and design.
255-
- **Implementation.** We'll provide hands-on support to implement our reference architectures.
285+
[![Learn More](https://img.shields.io/badge/learn%20more-success.svg?style=for-the-badge)][commercial_support]
256286

287+
Work directly with our team of DevOps experts via email, slack, and video conferencing.
257288

289+
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
258290

259-
## Terraform Module Development
260-
261-
Are you interested in custom Terraform module development? Submit your inquiry using [our form][module_development] today and we'll get back to you ASAP.
262-
291+
- **Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.
292+
- **Release Engineering.** You'll have end-to-end CI/CD with unlimited staging environments.
293+
- **Site Reliability Engineering.** You'll have total visibility into your apps and microservices.
294+
- **Security Baseline.** You'll have built-in governance with accountability and audit logs for all changes.
295+
- **GitOps.** You'll be able to operate your infrastructure via Pull Requests.
296+
- **Training.** You'll receive hands-on training so your team can operate what we build.
297+
- **Questions.** You'll have a direct line of communication between our teams via a Shared Slack channel.
298+
- **Troubleshooting.** You'll get help to triage when things aren't working.
299+
- **Code Reviews.** You'll receive constructive feedback on Pull Requests.
300+
- **Bug Fixes.** We'll rapidly work with you to fix any bugs in our projects.
263301

264302
## Slack Community
265303

266304
Join our [Open Source Community][slack] on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
267305

306+
## Discourse Forums
307+
308+
Participate in our [Discourse Forums][discourse]. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
309+
268310
## Newsletter
269311

270-
Signup for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
312+
Sign up for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
313+
314+
## Office Hours
315+
316+
[Join us every Wednesday via Zoom][office_hours] for our weekly "Lunch & Learn" sessions. It's **FREE** for everyone!
317+
318+
[![zoom](https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png")][office_hours]
271319

272320
## Contributing
273321

@@ -292,7 +340,7 @@ In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
292340

293341
## Copyright
294342

295-
Copyright © 2017-2019 [Cloud Posse, LLC](https://cpco.io/copyright)
343+
Copyright © 2017-2020 [Cloud Posse, LLC](https://cpco.io/copyright)
296344

297345

298346

@@ -359,33 +407,32 @@ Check out [our other projects][github], [follow us on twitter][twitter], [apply
359407
[sarkis_homepage]: https://github.com/sarkis
360408
[sarkis_avatar]: https://img.cloudposse.com/150x150/https://github.com/sarkis.png
361409

362-
363-
364410
[![README Footer][readme_footer_img]][readme_footer_link]
365411
[![Beacon][beacon]][website]
366412

367413
[logo]: https://cloudposse.com/logo-300x69.svg
368-
[docs]: https://cpco.io/docs
369-
[website]: https://cpco.io/homepage
370-
[github]: https://cpco.io/github
371-
[jobs]: https://cpco.io/jobs
372-
[hire]: https://cpco.io/hire
373-
[slack]: https://cpco.io/slack
374-
[linkedin]: https://cpco.io/linkedin
375-
[twitter]: https://cpco.io/twitter
376-
[testimonial]: https://cpco.io/leave-testimonial
377-
[newsletter]: https://cpco.io/newsletter
378-
[email]: https://cpco.io/email
379-
[commercial_support]: https://cpco.io/commercial-support
380-
[we_love_open_source]: https://cpco.io/we-love-open-source
381-
[module_development]: https://cpco.io/module-development
382-
[terraform_modules]: https://cpco.io/terraform-modules
383-
[readme_header_img]: https://cloudposse.com/readme/header/img?repo=cloudposse/terraform-aws-alb-ingress
384-
[readme_header_link]: https://cloudposse.com/readme/header/link?repo=cloudposse/terraform-aws-alb-ingress
385-
[readme_footer_img]: https://cloudposse.com/readme/footer/img?repo=cloudposse/terraform-aws-alb-ingress
386-
[readme_footer_link]: https://cloudposse.com/readme/footer/link?repo=cloudposse/terraform-aws-alb-ingress
387-
[readme_commercial_support_img]: https://cloudposse.com/readme/commercial-support/img?repo=cloudposse/terraform-aws-alb-ingress
388-
[readme_commercial_support_link]: https://cloudposse.com/readme/commercial-support/link?repo=cloudposse/terraform-aws-alb-ingress
414+
[docs]: https://cpco.io/docs?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=docs
415+
[website]: https://cpco.io/homepage?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=website
416+
[github]: https://cpco.io/github?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=github
417+
[jobs]: https://cpco.io/jobs?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=jobs
418+
[hire]: https://cpco.io/hire?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=hire
419+
[slack]: https://cpco.io/slack?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=slack
420+
[linkedin]: https://cpco.io/linkedin?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=linkedin
421+
[twitter]: https://cpco.io/twitter?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=twitter
422+
[testimonial]: https://cpco.io/leave-testimonial?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=testimonial
423+
[office_hours]: https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=office_hours
424+
[newsletter]: https://cpco.io/newsletter?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=newsletter
425+
[discourse]: https://ask.sweetops.com/?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=discourse
426+
[email]: https://cpco.io/email?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=email
427+
[commercial_support]: https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=commercial_support
428+
[we_love_open_source]: https://cpco.io/we-love-open-source?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=we_love_open_source
429+
[terraform_modules]: https://cpco.io/terraform-modules?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=terraform_modules
430+
[readme_header_img]: https://cloudposse.com/readme/header/img
431+
[readme_header_link]: https://cloudposse.com/readme/header/link?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=readme_header_link
432+
[readme_footer_img]: https://cloudposse.com/readme/footer/img
433+
[readme_footer_link]: https://cloudposse.com/readme/footer/link?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=readme_footer_link
434+
[readme_commercial_support_img]: https://cloudposse.com/readme/commercial-support/img
435+
[readme_commercial_support_link]: https://cloudposse.com/readme/commercial-support/link?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-alb-ingress&utm_content=readme_commercial_support_link
389436
[share_twitter]: https://twitter.com/intent/tweet/?text=terraform-aws-alb-ingress&url=https://github.com/cloudposse/terraform-aws-alb-ingress
390437
[share_linkedin]: https://www.linkedin.com/shareArticle?mini=true&title=terraform-aws-alb-ingress&url=https://github.com/cloudposse/terraform-aws-alb-ingress
391438
[share_reddit]: https://reddit.com/submit/?url=https://github.com/cloudposse/terraform-aws-alb-ingress

0 commit comments

Comments
 (0)