RavenDB-17135: add sanity wf tests, docs, fix linting and syntax rules

.github/workflows/tests_role_ravendb_node.yml

@@ -1,12 +1,72 @@
-name: ravendb_node role tests 
+name: CI 
 
 on:
   push:
     branches: [ master ]
   pull_request:
     branches: [ master ]
+  schedule:
+    - cron: "0 10 * * 1" # every Monday at 10:00 UTC
 
 jobs:
+  sanity:
+    name: Ansible Sanity Tests
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        include:
+          - python-version: "3.9"
+            ansible-core: stable-2.15
+          - python-version: "3.10"
+            ansible-core: stable-2.15
+          - python-version: "3.11"
+            ansible-core: stable-2.15
+
+          - python-version: "3.10"
+            ansible-core: stable-2.16
+          - python-version: "3.11"
+            ansible-core: stable-2.16
+          - python-version: "3.12"
+            ansible-core: stable-2.16
+
+          - python-version: "3.10"
+            ansible-core: stable-2.17
+          - python-version: "3.11"
+            ansible-core: stable-2.17
+          - python-version: "3.12"
+            ansible-core: stable-2.17
+
+          - python-version: "3.11"
+            ansible-core: devel
+          - python-version: "3.12"
+            ansible-core: devel
+          - python-version: "3.13"
+            ansible-core: devel
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Fix collection path for ansible-test #should be removed once we restructre
+        run: |
+          mkdir -p ansible_collections/ravendb/community
+          rsync -av --exclude ansible_collections ./ ansible_collections/ravendb/community
+          cd ansible_collections/ravendb/community
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install "ansible-core@https://github.com/ansible/ansible/archive/${{ matrix.ansible-core }}.tar.gz"
+
+      - name: Run ansible-test sanity
+        working-directory: ansible_collections/ravendb/community
+        run: |
+          ansible-test sanity --python ${{ matrix.python-version }} --docker -v --color
+
   test-debian-setup-scenarios:
     runs-on: ubuntu-latest
     steps:
@@ -118,7 +178,7 @@ jobs:
         - name: Build ansible galaxy collection
           run: |
             ansible-galaxy collection build .
-            ansible-galaxy collection install ./ravendb-community-*.tar.gz --force -p ./
+            ansible-galaxy collection install ./community-ravendb-*.tar.gz --force -p ./
 
         - name: Set up .NET environment variables
           run: |

CHANGELOG.md

@@ -0,0 +1,18 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+This project follows the [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) principles and the [Ansible collection changelog format](https://docs.ansible.com/ansible/latest/dev_guide/collections_changelogs.html).
+
+The full changelog is maintained in [changelogs/changelog.yml](./changelogs/changelog.yml).
+
+## [1.0.0] - Initial Release
+
+### Added
+- Initial release of the `community.ravendb` Ansible Collection.
+- Added `ravendb_node` role for setting up RavenDB servers.
+- Added `ravendb_python_client_prerequisites` role for managing Python dependencies.
+- Added modules:
+  - `community.ravendb.database` for managing RavenDB databases.
+  - `community.ravendb.index` for managing RavenDB indexes and index modes.
+  - `community.ravendb.node` for adding nodes to a RavenDB cluster.

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+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 and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq