From aa4ac9e4fe36ae9d4ac122e4ff88aadde804a49d Mon Sep 17 00:00:00 2001 From: Ronen Hilewicz Date: Fri, 30 Aug 2024 09:07:14 -0400 Subject: [PATCH 1/6] Create CODE_OF_CONDUCT.md --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..d767529 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# 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 +community@aserto.com. +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][homepage], +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). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From da536d9be98f76a670fa701dee575a737c998edf Mon Sep 17 00:00:00 2001 From: Ronen Hilewicz Date: Fri, 30 Aug 2024 09:09:55 -0400 Subject: [PATCH 2/6] Create CONTRIBUTING.md --- CONTRIBUTING.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..5b6c884 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,32 @@ +# Contributing to Aserto Helm Charts + +Welcome, and thank you for considering contributing to the Aserto Helm charts. +We encourage you to help out by raising issues, improving documentation, +fixing bugs, or adding new features + +If you're interested in contributing please start by reading this document. If +you have any questions at all, or don't know where to start, please reach out to +us on [Slack](https://asertocommunity.slack.com/). Please also take a look at our +[code of conduct](CODE_OF_CONDUCT.md), which details +how contributors are expected to conduct themselves as part of the Aserto community. + +## Contributing Code + +To contribute bug fixes or features to Aserto Go: + +1. Communicate your intent. +1. Make your changes. +1. Test your changes. +1. Update documentation and examples where appropriate. +1. Open a Pull Request (PR). + +Communicating your intent lets the project maintainers know that you intend +to contribute, and how. This sets you up for success - you can avoid duplicating +an effort that may already be underway, adding a feature that may be rejected, +or heading down a path that you would be steered away from at review time. The +best way to communicate your intent is via a detailed GitHub issue. Take a look +first to see if there's already an issue relating to the thing you'd like to +contribute. If there isn't, please raise a new one! Let us know what you'd like +to work on, and why. The Aserto Go maintainers can't always triage new issues +immediately, but we encourage you to bring them to our attention via +[Slack](https://asertocommunity.slack.com/). From 5dad213786f760c9e74d34770ca3f8b7c4497ddf Mon Sep 17 00:00:00 2001 From: Ronen Hilewicz Date: Fri, 30 Aug 2024 09:26:29 -0400 Subject: [PATCH 3/6] CODEOWNERS.md --- .github/CODEOWNERS.md | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 .github/CODEOWNERS.md diff --git a/.github/CODEOWNERS.md b/.github/CODEOWNERS.md new file mode 100644 index 0000000..f96d026 --- /dev/null +++ b/.github/CODEOWNERS.md @@ -0,0 +1,2 @@ +# Global owners +* @aserto-dev/admins From ff411d407505fc4538281893b9b7d895311aef7a Mon Sep 17 00:00:00 2001 From: Ronen Hilewicz Date: Fri, 30 Aug 2024 09:26:38 -0400 Subject: [PATCH 4/6] README.md: config in a parent chart. --- README.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/README.md b/README.md index abd6e2a..a116816 100644 --- a/README.md +++ b/README.md @@ -138,6 +138,37 @@ The top-level sections in the `values.yaml` file are: The `aserto` umbrella chart's [values.yaml](charts/aserto/values.yaml) file documents the available options. +To use the chart as a dependency in your own chart, add the following to the parent chart's `Chart.yaml`: +```yaml +dependencies: + - name: aserto + version: ~0.1.6 + repository: oci://ghcr.io/aserto-dev/helm + +``` +Then run `helm dep update` to download the chart and its dependencies. + +When using the `aserto` chart as a dependency the parent's `values.yaml` file should +keep the `global` values in place but move the other values into the `aserto` section. +For example: +```yaml +global: + aserto: + ports: + grpc: 8282 + https: 8383 + health: 8484 + mertics: 8585 + ... + +aserto: + directory: + rootDirectory: + database: + port: 5432 + ... +``` + ## Deployment To deploy the Aserto services, first create a `values.yaml` file with the desired configuration. From 14f24847adbedb79fd717268129c74c5eeed0e74 Mon Sep 17 00:00:00 2001 From: Ronen Hilewicz Date: Fri, 30 Aug 2024 12:55:11 -0400 Subject: [PATCH 5/6] README: separate db roles for root and tenant directories --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index a116816..1d2a875 100644 --- a/README.md +++ b/README.md @@ -44,13 +44,14 @@ Additionally, if the role has the `CREATEDB` option, the service can create the automatically at startup if they don't already exist. Without the `CREATEDB` option, you must create the databases manually before deploying the chart. -The following SQL commands can be used to create the role and databases: +The following SQL commands can be used to create the roles and databases: ```sql -CREATE ROLE aserto CREATEROLE LOGIN PASSWORD ''; +CREATE ROLE aserto_root CREATEROLE LOGIN PASSWORD ''; +CREATE ROLE aserto_tenant CREATEROLE LOGIN PASSWORD ''; -CREATE DATABASE aserto-ds OWNER = aserto TEMPLATE = template0; -CREATE DATABASE aserto-root-ds OWNER = aserto TEMPLATE = template0; +CREATE DATABASE "aserto-root-ds" OWNER = aserto_root TEMPLATE = template0; +CREATE DATABASE "aserto-ds" OWNER = aserto_tenant TEMPLATE = template0; ``` ### Kubernetes Secrets From cd4625c9160ce1ff0232275fb81fc252a9021746 Mon Sep 17 00:00:00 2001 From: Ronen Hilewicz Date: Thu, 5 Sep 2024 15:50:50 -0400 Subject: [PATCH 6/6] LICENSE --- LICENSE | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..4ff7a42 --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2021 Aserto 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.