Skip to content

Commit

Permalink
Initial Release
Browse files Browse the repository at this point in the history
  • Loading branch information
douglas-f committed Oct 4, 2023
0 parents commit 1743332
Show file tree
Hide file tree
Showing 96 changed files with 4,212 additions and 0 deletions.
3 changes: 3 additions & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# These owners will be the default owners for everything in the repo. Unless a later match takes precedence

* @douglas-f ksnavely-cf
27 changes: 27 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/enhancement-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Enhancement request
about: Suggest an idea for this project
title: ''
labels: ''
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
12 changes: 12 additions & 0 deletions .github/workflows/org-checkov.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
name: Org Checkov
on:
pull_request:
paths:
- '**.tf'
branches:
- main
workflow_call:

jobs:
check-markdown:
uses: Coalfire-CF/Actions/.github/workflows/org-checkov.yml@main
12 changes: 12 additions & 0 deletions .github/workflows/org-md-lint.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
name: Markdown Lint
on:
pull_request:
paths:
- '**.md'
branches:
- main
workflow_call:

jobs:
check-markdown:
uses: Coalfire-CF/Actions/.github/workflows/org-markdown-lint.yml@main
11 changes: 11 additions & 0 deletions .github/workflows/org-release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
name: Org Release
on:
pull_request:
types:
- closed
branches:
- main

jobs:
create-release:
uses: Coalfire-CF/Actions/.github/workflows/org-release.yml@main
8 changes: 8 additions & 0 deletions .github/workflows/org-terraform-docs.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
name: Org Terraform Docs
on:
pull_request:
workflow_call:

jobs:
terraform-docs:
uses: Coalfire-CF/Actions/.github/workflows/org-terraform-docs.yml@main
23 changes: 23 additions & 0 deletions .github/workflows/org-terraform-fmt.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
name: Terraform fmt

on:
push:
branches:
- main
pull_request:
branches:
- main

jobs:
verify:
name: Check Terraform Formatting
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: Setup Terraform
uses: hashicorp/setup-terraform@v1
with:
terraform_version: 1.5.0
- name: Run Terraform fmt
run: terraform fmt -check -recursive .
25 changes: 25 additions & 0 deletions .github/workflows/org-terraform-validate.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
name: Terraform Validate

on:
push:
branches:
- main
pull_request:
branches:
- main

jobs:
verify:
name: Validate Terraform Configuration
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: Setup Terraform
uses: hashicorp/setup-terraform@v1
with:
terraform_version: 1.5.0
- name: Initialise with no backend
run: terraform init -backend=false
- name: Validate the configuration
run: terraform validate
32 changes: 32 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Local .terraform directories
**/.terraform/*
.terraform.lock.hcl

# .tfstate files
*.tfstate
*.tfstate.*

# Crash log files
crash.log

# Ignore override files as they are usually used to override resources locally and so
# are not checked in
override.tf
override.tf.json
*_override.tf
*_override.tf.json

# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan
# example: *tfplan*

.idea
.idea/*
.vscode
.vscode/
*.iml
*.zip
.DS_Store

# Ansible
*.pub
*.ppk
72 changes: 72 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via issue,
email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
2. Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
3. Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.

## Coalfire Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we, as contributors and project maintainers, pledge to make participation in our project and our community a harassment-free experience for everyone.

## Our Values

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. Our community reflects our company values:

Respect: We believe in acknowledging the rights, beliefs, and perspectives of others.

Excellence: We endeavor to adopt best practices in everything we do.

Leadership: We encourage thought leadership and innovation.

Integrity: We uphold the highest ethical standards in all our interactions.

Teamwork: We believe in the power of working together to achieve our common goals.

Enthusiasm: We approach every task with energy and eagerness.

## Expected Behavior

Demonstrate empathy and kindness toward other people.

Be respectful of differing opinions, viewpoints, and experiences.

Offer and gracefully accept constructive feedback.

Show courtesy and respect in public and private communications.

Avoid personal attacks directed toward other contributors.

## Unacceptable Behavior

Any form of discrimination and harassment is unacceptable. This includes but is not
limited to; offensive comments related to gender, sexual orientation, race, religion, disability, physical appearance, or other protected categories.

Public or private harassment, deliberate intimidation, violence, or threats of.

Publishing others’ private information, such as a physical or email address, without their explicit permission.

• The use of sexualized language or imagery and unwelcome sexual attention or advances.

• Trolling, insulting/derogatory comments, and personal or political attacks.

## Reporting & Enforcement

We encourage all communities to resolve issues on their own whenever possible. If you are unable to resolve the matter for any reason, or if the behavior is threatening or harassing, report it. We are dedicated to providing an environment where participants feel welcome and safe. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <[email protected]>. All complaints will be reviewed and investigated promptly and fairly. Confidentiality will be maintained for the reporter of an incident.

We will use our discretion in determining when and how we follow up with reported incidents. Consequences of violating this code may include, but are not limited to, a temporary or permanent ban from project participation, removal of contributions, and reporting the incident to employers or legal authorities as appropriate.

This Code of Conduct is a living document and will evolve with the community. The project maintainers reserve the right to update this code as necessary. Any changes will be communicated to community members.
Binary file added Coalfire-Azure-RAMPpak.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
21 changes: 21 additions & 0 deletions License.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2023 Coalfire Systems, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Loading

0 comments on commit 1743332

Please sign in to comment.