Fix failing GHA ci

.github/release-drafter.yml

@@ -1,3 +1,5 @@
+# Copyright (c) CloudBees, Inc.
+
 name-template: 'v$RESOLVED_VERSION 🌈'
 tag-template: 'v$RESOLVED_VERSION'
 categories:

.github/workflows/markdown.links.config.json

@@ -0,0 +1,13 @@
+{
+	"ignorePatterns": [
+		{
+			"pattern": "^https://support.cloudbees.com/hc/en-us"
+		},
+		{
+			"pattern": "^https://github.com/cloudbees/terraform-aws-cloudbees-ci-eks-addon"
+		},
+		{
+			"pattern": "^https://university.cloudbees.com/"
+		}
+	]
+}

.github/workflows/md-link-checker.yml

@@ -1,4 +1,7 @@
-name: MD Links Checker
+# Copyright (c) CloudBees, Inc.
+---
+
+name: "Documentation: MD Links Checker"
 on:
   pull_request:
   push:

.github/workflows/release-drafter.yml

@@ -1,3 +1,6 @@
+# Copyright (c) CloudBees, Inc.
+---
+
 name: Release Drafter
 
 on:

.github/workflows/superlinter.yml

@@ -1,3 +1,4 @@
+# Copyright (c) CloudBees, Inc.
 ---
 
 name: "Code Quality: Super-Linter"

.github/workflows/terraform-docs.yml

@@ -1,3 +1,4 @@
+# Copyright (c) CloudBees, Inc.
 ---
 
 name: "Documentation: terraform-docs"

.github/workflows/terraform.yml

@@ -1,3 +1,4 @@
+# Copyright (c) CloudBees, Inc.
 ---
 
 name: "Code Quality: Terraform"

.pre-commit-config.yaml

@@ -1,4 +1,4 @@
-# Copyright (c) HashiCorp, Inc.
+# Copyright (c) CloudBees, Inc.
 
 fail_fast: false
 repos:

.terraform-docs.yml

@@ -1,5 +1,4 @@
-# Copyright (c) HashiCorp, Inc.
-# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) CloudBees, Inc.
 
 ---
 

CONTRIBUTING.md

@@ -18,4 +18,4 @@ Run `pre-commit run --all-files`
 
 ## Release Drafter
 
-This repository uses [Release Drafter](https://github.com/release-drafter/release-drafter) thus it is mandatory to label Pull Ruquest and recommended to use [Semantic Commit Messages](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716).
+This repository uses [Release Drafter](https://github.com/release-drafter/release-drafter) thus it is recommended to use [Semantic Commit Messages](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716) to ease labelling your Pull Request accordingly.

blueprints/getting-started/v4/README.md

@@ -1,6 +1,6 @@
 # HashiCorp Consul Add-on for AWS EKS
 
-> Get started with this add-on by reviewing the following example.
+> Get started with this add-on by reviewing the following example using [AWS EKS Blueprint v4](https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/v4.32.1).
 
 ## Overview
 

blueprints/getting-started/v5/README.md

@@ -0,0 +1,74 @@
+# HashiCorp Consul Add-on for AWS EKS
+
+> Get started with this add-on by reviewing the following example using [AWS EKS Blueprint v5](https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main).
+
+## Overview
+
+The code in this directory showcases an easy way to get started with the HashiCorp Consul Add-on for AWS EKS.
+
+* [main.tf](./main.tf) contains the AWS and Kubernetes resources needed to use this add-on.
+* [outputs.tf](./outputs.tf) defines outputs that make interacting with `kubectl` easier
+* [providers.tf](./providers.tf) defines the required Terraform (core) and Terraform provider versions
+* [variables.tf](./variables.tf) defines the variables needed to use this add-on.
+
+## Usage
+
+Make sure to export your required [AWS Environment Variables](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html) to your CLI before getting started. For
+
+  ```bash
+  export AWS_ACCESS_KEY_ID=... 
+  export AWS_SECRET_ACCESS_KEY=...
+  export AWS_SESSION_TOKEN=...
+  ```
+
+Alternatively
+
+  ```bash
+  export AWS_PROFILE=... 
+  ```
+
+Initialize the root module and any associated configuration for providers, review the resources that will be created and finally create the resources and deploy CloudBees CI to an EKS Cluster. For more detailed information, see the documentation for the [Terraform Core workflow](https://www.terraform.io/intro/core-workflow).
+
+  ```sh
+  terraform init -upgrade
+  terraform plan
+  terraform apply
+  ```
+
+Once the resources have been created, import the credentials to the `$home/.kube/config` by running in your terminal the outcome of the following command:
+
+  ```sh
+  eval $(terraform output --raw configure_kubectl)
+  ```
+
+Once you validate that:
+
+1. The CloudBees Operation Center Pod is running
+
+  ```sh
+  until kubectl get pod -n cloudbees-ci cjoc-0; do sleep 2 && echo "Waiting for Pod to get ready"; done; echo "OC Pod is Ready"
+  ```
+
+2. The Ingress Controller is ready and has assigned an `ADDRESS`
+
+  ```sh
+  until kubectl get ing -n cloudbees-ci cjoc; do sleep 2 && echo "Waiting for Ingress to get ready"; done; echo "Ingress Ready"
+  ```
+
+Get the URL for the CloudBees CI Console that you need to open in your browser:
+
+  ```sh
+  terraform output cjoc_url
+  ```
+
+Then, the CloudBees CI installation Wizard will be displayed asking for initial password that can obtained by:
+
+  ```sh
+  kubectl exec -n cloudbees-ci -ti cjoc-0 -- cat /var/jenkins_home/secrets/initialAdminPassword
+ ```
+
+Finally, install the suggested plugins and create the first admin user.
+
+<!-- BEGIN_TF_DOCS -->
+
+<!-- END_TF_DOCS -->

values.yml

@@ -1,5 +1,8 @@
+# Copyright (c) CloudBees, Inc.
+
 #https://artifacthub.io/packages/helm/cloudbees/cloudbees-core/
 #https://docs.cloudbees.com/docs/cloudbees-ci/latest/eks-install-guide/installing-eks-using-helm
+
 Subdomain: true
 OperationsCenter:
   JavaOpts: >-