Initial commit

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,121 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[info@bryk.io](mailto:info@bryk.io?subject=[GitHub]%20CoC%20Report).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.0, available at <https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+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.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. MacOS 10.15.6]
+ - Browser [e.g. chrome, safari]
+ - Application version [e.g. 0.5.2]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+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.
+
+**Related Issues (if none, remove this section)**
+- #...

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+### Description
+
+Please explain the changes you made here:
+
+- [ ] A description of the problem you're trying to solve
+- [ ] An overview of the suggested solution
+- [ ] If the feature changes current behavior, reasons why your solution is better
+
+### Checklist
+
+Before you submit a pull request, please make sure you have to following:
+
+- [ ] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). Don't request your master!
+- [ ] Make sure you are making a pull request against the **canary branch** (left side). Also you should start *your branch* off *our canary*
+- [ ] Code compiles correctly
+- [ ] All existing (and new) tests passed
+- [ ] Your code should contain tests relevant for the problem you are solving
+- [ ] Extend or adjust the documentation, if necessary
+- [ ] All commit messages are properly formatted and descriptive
+- [ ] Code complies with exinting style guides

.github/SECURITY.md

@@ -0,0 +1,34 @@
+# Security Policy
+
+Please report to us any security issues you find.
+
+All security bugs should be reported by email to [info@bryk.io](mailto:info@bryk.io?subject=[GitHub]%20Security%20Report).
+This mail is delivered to a small security team. Your email will be acknowledged
+within 24 hours, and you'll receive a more detailed response to your email within
+72 hours indicating the next steps in handling your report.
+
+After the initial reply to your report, the security team will endeavor to keep you
+informed of the progress being made towards a fix and full announcement. These updates
+will be sent at least every five days. In reality, this is more likely to be every
+24-48 hours.
+
+## Responsible Disclosure Program
+
+This project uses the following disclosure process:
+
+1. Once the security report is received it is assigned a primary handler. This person
+coordinates the fix and release process.
+
+2. The issue is confirmed and a list of affected software is determined.
+
+3. Code is audited to find any potential similar problems.
+
+4. If it is determined, in consultation with the submitter, that a CVE-ID is required,
+the primary handler will obtain one.
+
+5. Fixes are prepared for, at least, the two most recent major releases and the head/master revision.
+
+This process can take some time, especially when coordination is required with maintainers
+of other projects. Every effort will be made to handle the bug in as timely a manner as possible,
+however it's important that we follow the process described above to ensure that disclosures
+are handled consistently and responsibly.

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+updates:
+  # Github Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"

.github/workflows/maintenance.yml

@@ -0,0 +1,25 @@
+name: "maintenance"
+on:
+  schedule:
+    - cron: "0 0 * * *"
+jobs:
+  stale:
+    name: "close stale issues and pull requests"
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v3
+        with:
+          # On the 'debug' mode the action will not perform any operation.
+          # Add the secret ACTIONS_STEP_DEBUG with a value of 'true' in the repository.
+          debug-only: false
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          days-before-stale: 45
+          days-before-close: 5
+          stale-issue-label: 'stale'
+          stale-pr-label: 'stale'
+          exempt-issue-labels: 'help wanted,awaiting approval,work in progress'
+          exempt-pr-labels: 'help wanted,awaiting approval,work in progress'
+          stale-issue-message: 'This issue has been marked as **stale** because it has not registered any activity during the last 45 days. If the **stale** label is not removed or no activity is registered, this will be automatically closed in 5 days.'
+          close-issue-message: 'This issue has been closed automatically after not registering any activity for 50 consecutive days.'
+          stale-pr-message: 'This pull request has been marked as **stale** because it has not registered any activity during the last 45 days. If the **stale** label is not removed or no activity is registered, this will be automatically closed in 5 days.'
+          close-pr-message: 'This pull request has been closed automatically after not registering any activity for 50 consecutive days.'

.github/workflows/publish.yml

@@ -0,0 +1,31 @@
+name: publish
+on:
+  push:
+    tags:
+      - '*'
+jobs:
+  # Publish project package(s)
+  publish:
+    name: publish package
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    if: startsWith(github.ref, 'refs/tags/')
+    steps:
+      # Checkout code
+      - name: Checkout repository
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+
+      # Use goreleaser to create the new release
+      - name: Create release
+        uses: goreleaser/goreleaser-action@v2.6.1
+        if: startsWith(github.ref, 'refs/tags/')
+        with:
+          version: latest
+          args: release --rm-dist --skip-validate
+        env:
+          # https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow
+          GITHUB_TOKEN: ${{ secrets.ACCESS_TOKEN }}
+          # Login of the user that initiated the workflow run
+          GITHUB_USER: ${{ github.actor }}

.gitignore

@@ -0,0 +1,28 @@
+# Generals
+.DS_Store
+.idea
+*.iml
+.code
+
+# Deps
+vendor/**
+
+# NodeJS
+node_modules
+package-lock.json
+build
+
+# PKI
+*.crt
+*.csr
+*.cer
+*.pem
+*.key
+!**/testdata/*.cer
+!**/testdata/*.pem
+
+# Secret files
+**/*secret*
+
+# Temp file
+tmp

.goreleaser.yml

@@ -0,0 +1,32 @@
+project_name: chart-deploy-action
+before:
+  hooks:
+    - docker login ghcr.io -u {{ .Env.GITHUB_USER }} -p {{ .Env.GITHUB_TOKEN }}
+build:
+  # this is required since we are not building any Go binaries
+  skip: true
+source:
+  enabled: true
+changelog:
+  sort: asc
+  filters:
+    exclude:
+      - '^docs:'
+      - '^test:'
+      - typo
+dockers:
+  -
+    dockerfile: Dockerfile
+    skip_push: false
+    extra_files:
+      - chart-deploy.sh
+    image_templates:
+      - "ghcr.io/bryk-io/{{ .ProjectName }}:{{ .Version }}"
+      - "ghcr.io/bryk-io/{{ .ProjectName }}:latest"
+    build_flag_templates:
+      - "--pull"
+      - "--label=org.opencontainers.image.title={{ .ProjectName }}"
+      - "--label=org.opencontainers.image.created={{ .CommitDate }}"
+      - "--label=org.opencontainers.image.revision={{ .FullCommit }}"
+      - "--label=org.opencontainers.image.version={{ .Version }}"
+      - "--label=org.opencontainers.image.source=https://github.com/bryk-io/{{ .ProjectName }}"

Dockerfile

@@ -0,0 +1,19 @@
+FROM alpine:latest
+
+RUN \
+  # kubectl
+  wget https://dl.k8s.io/release/v1.21.1/bin/linux/amd64/kubectl -O /usr/bin/kubectl && \
+  chmod 755 /usr/bin/kubectl && \
+  # helm
+  wget https://get.helm.sh/helm-v3.6.0-linux-amd64.tar.gz && \
+  tar -xvzf helm-v3.6.0-linux-amd64.tar.gz && \
+  mv linux-amd64/helm /usr/bin/. && \
+  chmod 755 /usr/bin/helm && \
+  rm -rf linux-amd64/ helm-v3.6.0-linux-amd64.tar.gz && \
+  # terraform
+  wget https://releases.hashicorp.com/terraform/1.0.0/terraform_1.0.0_linux_amd64.zip && \
+  unzip terraform_1.0.0_linux_amd64.zip && \
+  mv terraform /usr/bin/. && \
+  rm terraform_1.0.0_linux_amd64.zip
+
+COPY chart-deploy.sh /bin/chart-deploy