add account-settings module (#2)

Co-authored-by: nitrocode <nitrocode@users.noreply.github.com>
Co-authored-by: cloudpossebot <11232728+cloudpossebot@users.noreply.github.com>

Author: 3 people

.github/CODEOWNERS

@@ -15,8 +15,8 @@
 
 # Cloud Posse must review any changes to standard context definition,
 # but some changes can be rubber-stamped.
-**/*.tf       @cloudposse/engineering @cloudposse/approvers
-README.yaml   @cloudposse/engineering @cloudposse/approvers
+**/*.tf       @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers
+README.yaml   @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers
 README.md     @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers
 docs/*.md     @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers
 

.github/auto-release.yml

@@ -17,6 +17,7 @@ version-resolver:
     - 'bugfix'
     - 'bug'
     - 'hotfix'
+    - 'no-release'
   default: 'minor'
 
 categories:
@@ -46,7 +47,7 @@ template: |
 
 replacers:
 # Remove irrelevant information from Renovate bot
-- search: '/---\s+^#.*Renovate configuration(?:.|\n)*?This PR has been generated .*/gm'
+- search: '/(?<=---\s+)+^#.*(Renovate configuration|Configuration)(?:.|\n)*?This PR has been generated .*/gm'
   replace: ''
 # Remove Renovate bot banner image
 - search: '/\[!\[[^\]]*Renovate\][^\]]*\](\([^)]*\))?\s*\n+/gm'

.github/workflows/auto-release.yml

@@ -3,17 +3,24 @@ name: auto-release
 on:
   push:
     branches:
-    - master
+      - main
+      - master
+      - production
 
 jobs:
   publish:
     runs-on: ubuntu-latest
     steps:
-    # Drafts your next Release notes as Pull Requests are merged into "master"
-    - uses: release-drafter/release-drafter@v5
-      with:
-        publish: true
-        prerelease: false
-        config-name: auto-release.yml
-      env:
-        GITHUB_TOKEN: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }}
+      # Get PR from merged commit to master
+      - uses: actions-ecosystem/action-get-merged-pull-request@v1
+        id: get-merged-pull-request
+        with:
+          github_token: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }}
+      # Drafts your next Release notes as Pull Requests are merged into "main"
+      - uses: release-drafter/release-drafter@v5
+        with:
+          publish: ${{ !contains(steps.get-merged-pull-request.outputs.labels, 'no-release') }}
+          prerelease: false
+          config-name: auto-release.yml
+        env:
+          GITHUB_TOKEN: ${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }}

.github/workflows/validate-codeowners.yml

@@ -1,5 +1,7 @@
 name: Validate Codeowners
 on:
+  workflow_dispatch:
+
   pull_request:
 
 jobs:

.gitignore

@@ -6,6 +6,7 @@
 *.tfstate.*
 .terraform
 .terraform.tfstate.lock.info
+.terraform.lock.hcl
 
 **/.idea
 **/*.iml

README.md

@@ -5,94 +5,111 @@
 #
 
 # Name of this project
-name: terraform-example-module
+name: terraform-aws-api-gateway
+
+# Tags of this project
+tags:
+  - terraform
+  - terraform-modules
+  - api-gateway
+  - rest-api
+# Categories of this project
+categories:
+  - terraform-modules/api-gateway
 
 # Logo for this project
 #logo: docs/logo.png
 
 # License of this project
 license: "APACHE2"
 
-# Copyrights
-copyrights:
-  - name: "Cloud Posse, LLC"
-    url: "https://cloudposse.com"
-    year: "2020"
-
 # Canonical GitHub repo
-github_repo: cloudposse/terraform-example-module
+github_repo: cloudposse/terraform-aws-api-gateway
 
 # Badges to display
 badges:
   - name: "Latest Release"
-    image: "https://img.shields.io/github/release/cloudposse/terraform-example-module.svg"
-    url: "https://github.com/cloudposse/terraform-example-module/releases/latest"
+    image: "https://img.shields.io/github/release/cloudposse/terraform-api-gateway-platform.svg"
+    url: "https://github.com/cloudposse/terraform-api-gateway-platform/releases/latest"
   - name: "Slack Community"
     image: "https://slack.cloudposse.com/badge.svg"
     url: "https://slack.cloudposse.com"
-  - name: "Discourse Forum"
-    image: "https://img.shields.io/discourse/https/ask.sweetops.com/posts.svg"
-    url: "https://ask.sweetops.com/"
 
-# List any related terraform modules that this module may be used with or that this module depends on.
 related:
-  - name: "terraform-null-label"
-    description: "Terraform module designed to generate consistent names and tags for resources. Use terraform-null-label to implement a strict naming convention."
-    url: "https://github.com/cloudposse/terraform-null-label"
-
-# List any resources helpful for someone to get started. For example, link to the hashicorp documentation or AWS documentation.
-references:
-  - name: "Terraform Standard Module Structure"
-    description: "HashiCorp's standard module structure is a file and directory layout we recommend for reusable modules distributed in separate repositories."
-    url: "https://www.terraform.io/docs/modules/index.html#standard-module-structure"
-  - name: "Terraform Module Requirements"
-    description: "HashiCorp's guidance on all the requirements for publishing a module. Meeting the requirements for publishing a module is extremely easy."
-    url: "https://www.terraform.io/docs/registry/modules/publish.html#requirements"
-  - name: "Terraform `random_integer` Resource"
-    description: "The resource random_integer generates random values from a given range, described by the min and max attributes of a given resource."
-    url: "https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/integer"
-  - name: "Terraform Version Pinning"
-    description: "The required_version setting can be used to constrain which versions of the Terraform CLI can be used with your configuration"
-    url: "https://www.terraform.io/docs/configuration/terraform.html#specifying-a-required-terraform-version"
+  - name: "terraform-yaml-config"
+    description:
+      "Terraform module to convert local and remote YAML configuration templates into Terraform lists and maps"
+    url: "https://github.com/cloudposse/terraform-yaml-config"
 
 # Short description of this project
 description: |-
-  This is `terraform-example-module` project provides all the scaffolding for a typical well-built Cloud Posse module. It's a template repository you can
-  use when creating new repositories.
+  Terraform module to provision API Gatway resources.
+
+  The root module creates an API Gateway [REST API](https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-rest-api.html) 
+  along with configuring tracing, logging, and metrics.
+
+  The module also consists of the following submodules:
+
+    - [account-settings](modules/account-settings) - to provision account-level settings for logging and metrics for API Gateway
+    ```
 
-# Introduction to the project
 #introduction: |-
-#  This is an introduction.
 
-# How to use this module. Should be an easy example to copy and paste.
+references:
+  - name: "API Gateway CloudWatch Logging"
+    description:
+      "To enable CloudWatch Logs, you must grant API Gateway permission to read and write logs to CloudWatch for your
+      account."
+    url: "https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-logging.html"
+
+  - name: "Create a monitor"
+    description: "Create datadog monitors"
+    url: "https://docs.datadoghq.com/api/v1/monitors/#create-a-monitor"
+
+  - name: "Terraform Datadog role resources"
+    description: "Provides a Datadog role resource. Used to create and manage Datadog roles"
+    url: "https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/role"
+
+  - name: "Datadog permissions"
+    description:
+      "Use this data source to retrieve the list of Datadog permissions by name and their corresponding ID, for use in
+      the role resource"
+    url: "https://registry.terraform.io/providers/DataDog/datadog/latest/docs/data-sources/permissions"
+
+  - name: "Role Based Access Control"
+    description:
+      "Roles categorize users and define what account permissions those users have, such as what data they can read or
+      what account assets they can modify"
+    url: "https://docs.datadoghq.com/account_management/rbac"
+
+  - name: "Managing Multiple-Organization Accounts"
+    description:
+      "It is possible to manage multiple child-organizations from one parent-organization account. This is typically
+      used by Managed Service Providers that have customers which should not have access to each others' data"
+    url: "https://docs.datadoghq.com/account_management/multi_organization"
+
+# How to use this project
 usage: |-
-  For a complete example, see [examples/complete](examples/complete).
-  
-  For automated tests of the complete example using [bats](https://github.com/bats-core/bats-core) and [Terratest](https://github.com/gruntwork-io/terratest)
-  (which tests and deploys the example on AWS), see [test](test).
+
+  Setup the account-level settings for logging and metrics for API Gateway:
 
   ```hcl
-  module "example" {
-    source = "https://github.com/cloudposse/terraform-example-module.git?ref=master"
-    example = "Hello world!"
+  module "api_gateway_account_settgings" {
+    source  = "cloudposse/api-gateway/aws//modules/account-settings"
+    # version = "x.x.x"
+
+    context = module.this.context
   }
   ```
 
-# Example usage
 examples: |-
-  Here is an example of using this module:
-  - [`examples/complete`](https://github.com/cloudposse/terraform-example-module/) - complete example of using this module
-
-# How to get started quickly
-#quickstart: |-
-#  Here's how to get started...
+  Review the [examples](examples) folder to see how to use the API Gateway modules.
 
-# Other files to include in this README from the project folder
 include:
   - "docs/targets.md"
   - "docs/terraform.md"
 
 # Contributors to this project
 contributors:
-  - name: "Erik Osterman"
-    github: "osterman"
+  - name: "Matt Calhoun"
+    github: "mcalhoun"