Added Ansible Validated Content for Automation CoP (#24)

* Added Ansible Validated Content for Automation CoP Signed-off-by: Andrew Block <[email protected]> * Updated broken link Signed-off-by: Andrew Block <[email protected]> * Fix broken links Signed-off-by: Andrew Block <[email protected]> * Disable external checking Signed-off-by: Andrew Block <[email protected]> Signed-off-by: Andrew Block <[email protected]>
redhat-cop · Dec 1, 2022 · 933aeb7 · 933aeb7
1 parent ead418d
commit 933aeb7
Show file tree

Hide file tree

Showing 7 changed files with 26 additions and 5 deletions.
diff --git a/.github/workflows/test-doc-build.yml b/.github/workflows/test-doc-build.yml
@@ -22,4 +22,4 @@ jobs:
       - name: Build and Test
         run: |
           bundle exec jekyll build
-          bundle exec htmlproofer ./_site
+          bundle exec htmlproofer --disable-external=true ./_site
diff --git a/ci/linting-testing-helm-charts.md b/ci/linting-testing-helm-charts.md
@@ -157,9 +157,7 @@ rules:
 Now that we have reviewed each of the files required for ct, let's explore an example.
 
 ## Example
-For this example, we will look at the [Pelorus repo](https://github.com/redhat-cop/pelorus). This repo has two separate workflows under [.github/workflows](https://github.com/redhat-cop/pelorus/tree/master/.github/workflows), one specifically for ct and another for building the app (though both workflows could be combined). Here is an example ct build - https://github.com/redhat-cop/pelorus/runs/894996440?check_suite_focus=true.
-
-Let’s look closely at the Lint task of the [ct example](https://github.com/redhat-cop/pelorus/runs/894996440?check_suite_focus=true). After the workflow clones the source code, the “Lint Helm charts” step begins. When ct detects chart changes, you’ll see a message similar to the following.
+For this example, we will look at the [Pelorus repo](https://github.com/konveyor/pelorus). There is a [Makefile](https://github.com/konveyor/pelorus/blob/master/Makefile) with a dedicated target called `chart-lint`. When ct detects chart changes, you’ll see a message similar to the following.
 
 ```
  Charts to be processed:

diff --git a/ci/repository-request-access.md b/ci/repository-request-access.md
@@ -133,4 +133,4 @@ When complete, submit a new Pull Request against the repository as described in
 
 Content produced by the CoP can be published to Ansible Galaxy and an API key can be provided to aid in the publishing of content. Access can be requested through the [issue request process](https://github.com/redhat-cop/org/issues/new/choose) described earlier.
 
-For repositories hosted on GitHub within the CoP organization, a [Secret](https://docs.github.com/en/rest/reference/actions#secrets) called _ANSIBLE_GALAXY_APIKEY_ can be made available within your repository to use as part of a [GitHub Action workflow](https://docs.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#about-workflows). Be sure to include the desire to leverage this option as part of your request.
+For repositories hosted on GitHub within the CoP organization, a `Secret` called _ANSIBLE_GALAXY_APIKEY_ can be made available within your repository to use as part of a `GitHub Action workflow`. Be sure to include the desire to leverage this option as part of your request.
diff --git a/cop/automation-cop/index.md b/cop/automation-cop/index.md
@@ -0,0 +1,8 @@
+---
+title: Automation Community of Practice
+---
+
+Resources provided by the Automation Community of Practice.
+
+* [Ansible Validated Content Submission](./validated-content-submit.html)
+
diff --git a/cop/automation-cop/validated-content-submit.md b/cop/automation-cop/validated-content-submit.md
@@ -0,0 +1,6 @@
+---
+title: Ansible Validated Content Submission
+---
+
+
+<iframe src="https://docs.google.com/forms/d/e/1FAIpQLScVYHuJpJPKMsSpgv9c8JXx5zvAbmw1UkdvPuKtd_F6DtVd4Q/viewform?embedded=true" width="640" align="middle" height="1742" frameborder="0" marginheight="0" marginwidth="0">Loading…</iframe>
diff --git a/cop/index.md b/cop/index.md
@@ -0,0 +1,8 @@
+---
+title: Communities at Red Hat Content
+---
+
+This section contains content that are specific to each Red Hat Community of Practice.
+
+* [Automation Community of Practice](./automation-cop)
+
diff --git a/index.md b/index.md
@@ -12,4 +12,5 @@ This wiki site outlines the workflows for contributing to our various Community
 
 * [Red Hat CoP Repository Map](./repos/)
 * [Repository Contribution Guidelines](./contrib/)
+* [Red Hat CoP Specific Content](./cop/)
 * [How to implement continuous integration for redhat-cop repositories](./ci/)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -133,4 +133,4 @@ When complete, submit a new Pull Request against the repository as described in

		Content produced by the CoP can be published to Ansible Galaxy and an API key can be provided to aid in the publishing of content. Access can be requested through the [issue request process](https://github.com/redhat-cop/org/issues/new/choose) described earlier.

		For repositories hosted on GitHub within the CoP organization, a [Secret](https://docs.github.com/en/rest/reference/actions#secrets) called _ANSIBLE_GALAXY_APIKEY_ can be made available within your repository to use as part of a [GitHub Action workflow](https://docs.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#about-workflows). Be sure to include the desire to leverage this option as part of your request.
		For repositories hosted on GitHub within the CoP organization, a `Secret` called _ANSIBLE_GALAXY_APIKEY_ can be made available within your repository to use as part of a `GitHub Action workflow`. Be sure to include the desire to leverage this option as part of your request.