Initial commit of the SpiceDB validation GHA

.github/workflows/cla.yaml

@@ -0,0 +1,29 @@
+---
+name: "CLA Assistant"
+on:
+  issue_comment:
+    types:
+      - "created"
+  pull_request_target:
+    types:
+      - "opened"
+      - "closed"
+      - "synchronize"
+
+jobs:
+  CLAssistant:
+    runs-on: "ubuntu-latest"
+    steps:
+      - name: "CLA Assistant"
+        if: "(github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target'"
+        uses: "cla-assistant/github-action@v2.1.3-beta"
+        env:
+          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
+          PERSONAL_ACCESS_TOKEN: "${{ secrets.CLA_ASSISTANT_ACCESS_TOKEN }}"
+        with:
+          remote-organization-name: "authzed"
+          remote-repository-name: "cla"
+          path-to-signatures: "v1/signatures.json"
+          path-to-document: "https://github.com/authzed/cla/blob/main/v1/icla.md"
+          branch: "main"
+          allowlist: "authzedbot,dependabot-bot"

.github/workflows/test.yaml

@@ -0,0 +1,18 @@
+---
+name: "test"
+
+on:
+  - "push"
+  - "pull_request"
+
+jobs:
+  test:
+    runs-on: "ubuntu-latest"
+    steps:
+      - uses: "actions/checkout@v2"
+      - uses: "bewuethr/yamllint-action@v1.1.1"
+        with:
+          config-file: ".yamllint"
+      - uses: "./"
+        with:
+          validationfile: "test-schema.zaml"

.yamllint

@@ -0,0 +1,11 @@
+# vim: ft=yaml
+---
+yaml-files:
+  - "*.yaml"
+  - "*.zaml"
+  - "*.yml"
+  - ".yamllint"
+extends: "default"
+rules:
+  quoted-strings: "enable"
+  line-length: "disable"

CODE-OF-CONDUCT.md

@@ -0,0 +1,22 @@
+As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery
+- Personal attacks
+- Trolling or insulting/derogatory comments
+- Public or private harassment
+- Publishing other’s private information, such as physical or electronic addresses, without explicit permission
+- Other unethical or unprofessional conduct
+
+Project maintainers 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.
+By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project.
+Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.2.0, available at https://www.contributor-covenant.org/version/1/2/0/code-of-conduct.html

CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# How to contribute
+
+## Communication
+
+- Issues: [GitHub](https://github.com/authzed/action-spicedb/issues)
+- Email: [Google Groups](https://groups.google.com/g/authzed-oss)
+- Discord: [Zanzibar Discord](https://discord.gg/jTysUaxXzM)
+
+All communication must follow our [Code of Conduct].
+
+[Code of Conduct]: CODE-OF-CONDUCT.md
+
+## Creating issues
+
+If any part of the project has a bug or documentation mistakes, please let us know by opening an issue.
+All bugs and mistakes are considered very seriously, regardless of complexity.
+
+Before creating an issue, please check that an issue reporting the same problem does not already exist.
+To make the issue accurate and easy to understand, please try to create issues that are:
+
+- Unique -- do not duplicate existing bug report.
+  Deuplicate bug reports will be closed.
+- Specific -- include as much details as possible: which version, what environment, what configuration, etc.
+- Reproducible -- include the steps to reproduce the problem.
+  Some issues might be hard to reproduce, so please do your best to include the steps that might lead to the problem.
+- Isolated -- try to isolate and reproduce the bug with minimum dependencies.
+  It would significantly slow down the speed to fix a bug if too many dependencies are involved in a bug report.
+  Debugging external systems that rely on this project is out of scope, but guidance or help using the project itself is fine.
+- Scoped -- one bug per report.
+  Do not follow up with another bug inside one report.
+
+It may be worthwhile to read [Elika Etemad’s article on filing good bug reports][filing-good-bugs] before creating a bug report.
+
+Maintainers might ask for further information to resolve an issue.
+
+[filing-good-bugs]: http://fantasai.inkedblade.net/style/talks/filing-good-bugs/
+
+## Contribution flow
+
+This is a rough outline of what a contributor's workflow looks like:
+
+- Create an issue
+- Fork the project
+- Create a [feature branch]
+- Push changes to your branch
+- Submit a pull request
+- Respond to feedback from project maintainers
+
+Creating new issues is one of the best ways to contribute.
+You have no obligation to offer a solution or code to fix an issue that you open.
+If you do decide to try and contribute something, please submit an issue first so that a discussion can occur to avoid any wasted efforts.
+
+[feature branch]: https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow
+
+## Legal requirements
+
+In order to protect both you and ourselves, all commits will require an explicit sign-off that acknowledges the [DCO].
+
+Sign-off commits end with the following line:
+
+```
+Signed-off-by: Random J Developer <random@developer.example.org>
+```
+
+This can be done by using the `--signoff` (or `-s` for short) git flag to append this automatically to your commit message.
+If you have already authored a commit that is missing the signed-off, you can amend or rebase your commits and force push them to GitHub.
+
+[DCO]: /DCO

DCO

@@ -0,0 +1,37 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.

Dockerfile

@@ -0,0 +1,8 @@
+FROM quay.io/authzed/zed:latest as base
+
+FROM ubuntu:22.04
+COPY --from=base /usr/local/bin/zed /zed
+RUN chmod +x /zed
+COPY entrypoint.sh .
+RUN chmod +x entrypoint.sh
+ENTRYPOINT ["bash", "./entrypoint.sh"]