Merge pull request #890 from TheLunarCompany/cloud-532-backend-logic-…

…tests

fix: active flows/quotas leftovers

.dcignore

@@ -0,0 +1,22 @@
+# Write glob rules for ignored files.
+# Check syntax on https://deepcode.freshdesk.com/support/solutions/articles/60000531055-how-can-i-ignore-files-or-directories-
+# Check examples on https://github.com/github/gitignore
+
+# Hidden directories
+.*/
+.history/
+ **.history/
+
+# No Validation
+readme-files/*
+sandbox/grafana/*
+sandbox/lunar-proxy/*
+sandbox/prometheus/*
+
+# Tests directories
+**test**
+interceptors/integration-tests/*
+interceptors/lunar-ts-interceptor/test-client/*
+interceptors/lunar-python-interceptor/test-client/*
+interceptors/lunar-java-interceptor/test-client/*
+proxy/integration-tests/*

.github/workflows/generate-public-release.yml

@@ -0,0 +1,48 @@
+name: Create Public Draft Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      service:
+        description: "Release for service type"
+        required: true
+        type: string
+      tag:
+        description: "Release Tag"
+        required: true
+        type: string
+      name:
+        description: "Release Name"
+        required: true
+        type: string
+      body:
+          description: "Release Message"
+          required: true
+          type: string
+
+permissions:
+  contents: write
+
+jobs:
+  create_release:
+    runs-on: ubuntu-22.04
+
+    steps:
+      - name: Decode Base64
+        run: |
+          decoded_string=$(echo "${{ inputs.body }}" | base64 -d)
+          
+          echo "Decoded string: $decoded_string"
+
+          cat > ${{ github.workspace }}/body.txt <<-EOF
+          $decoded_string
+          EOF
+
+      - name: Create Public Draft Release
+        uses: softprops/action-gh-release@v1
+        with:
+          body_path: ${{ github.workspace }}/body.txt
+          draft: true
+          name: "${{ inputs.name }}"
+          tag_name: "${{ inputs.tag }}"
+          token: ${{ secrets.GITHUB_TOKEN }}

CODE_OF_CONDUCT.md

@@ -0,0 +1,135 @@
+# LUNAR COMMUNITY CODE OF CONDUCT
+
+## Summary
+
+Amongst the boundless expanse of our open-source galaxy and our home moon of
+Lunar, there are many people from different backgrounds. To make as many people
+ welcome to Lunar as we can, please:
+
+- Treat everyone with respect and kindness.
+- Be thoughtful in how you communicate.
+- Don’t be destructive or inflammatory.
+- If you encounter an issue, please mail us at
+  [[email protected]](mailto:[email protected]).
+
+## 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, caste, color, 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
+
+If you are unsure whether a behavior is considered welcoming and respectful,
+talk to us before proceeding.
+
+## 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. Examples of community spaces
+include (but are not limited to) GitHub issues or Pull Request conversations,
+our online communities (Slack and/or Discord), and emails to community members.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[[email protected]](mailto:[email protected]). 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, version 2.1
+available at](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

CONTRIBUTING.md

@@ -0,0 +1,74 @@
+# Contributing to Lunar Proxy
+
+Welcome, fellow space explorer! We appreciate your interest in contributing to
+Lunar Proxy. 🧑‍🚀
+
+Your contributions will help us take a giant leap towards a more reliable and
+secure browsing experience.
+
+![An astronaut writing code on a laptop](/readme-files/contributor.png "An astronaut writing code on a laptop")
+
+## How can I contribute?
+
+> Note: Before embarking on your mission, please review our [Code of Conduct](./CODE_OF_CONDUCT.md).
+
+There are many ways you can contribute to Lunar Proxy. You can:
+
+- [Report a bug](https://github.com/TheLunarCompany/lunar-proxy/issues/new/choose)
+- [Request a new feature](https://github.com/TheLunarCompany/lunar-proxy/issues/new/choose)
+- [Contact us](https://www.lunar.dev/#footer-contact)
+
+## How can I contribute code?
+
+To ensure a smooth journey aboard our lunar mission, please follow these guidelines:
+
+### Feature Branch Approach
+
+We employ a feature branch approach for development. This approach allows
+contributors to work on new features or bug fixes in isolated branches before
+merging them into the main codebase.
+
+Every feature or bug should have a corresponding GitHub issue. Before
+starting work on a new feature, please check if an issue exists. If not, [create
+](https://github.com/TheLunarCompany/lunar-proxt/issues/new/choose) a new one to
+track the progress.
+
+### Branch Naming Convention
+
+When creating a branch for a new feature or bug fix, please use the following
+naming convention:
+
+```text
+<username>.<issue#>-<description>
+```
+
+We have a handy script which automates the branch creation process. Feel free to
+use it and embark on your coding expedition:
+
+```sh
+./scripts/new_branch.sh
+```
+
+### Opening a Pull Request
+
+When you believe your code is ready for review and integration into the main
+codebase, open a pull request (PR) on GitHub. You can do this by running:
+
+```sh
+gh pr create
+```
+
+We encourage you to seek early feedback, even if your code is not yet ready to
+be merged. In such cases, mark the pull request as a draft to indicate its
+work-in-progress nature.
+
+### Squash and Merge
+
+Once your PR has been reviewed and approved, and all continuous integration (CI)
+checks have successfully passed, it's time for the ultimate space maneuver:
+Squash and Merge. This operation combines all your commits into a single,
+coherent commit, preserving the integrity of our code history.
+
+Thank you for joining us on this cosmic journey. Together, we'll propel Lunar to
+new heights and conquer the challenges that lie ahead. Happy coding, and may the
+lunar light guide your way! 🌖

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Lunar.dev
+
+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.