Update README.md

.github/workflows/pytest.yml

@@ -0,0 +1,31 @@
+name: Pytest Checks
+
+on:
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  pytest:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ['3.10', '3.11', '3.12', '3.13']
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install uv and dependencies
+        run: |
+          pip install uv
+          uv sync
+
+      - name: Run pytest
+        run: |
+          uv run pytest

GEMINI.md

@@ -0,0 +1,3 @@
+## Gemini Added Memories
+- Envars is a command-line tool for managing your application's configuration as code, handling
+  environment variables across different environments, locations(accounts and projects)

README.md

@@ -132,6 +132,7 @@ environment_variables:
 
 Here are some ideas for future enhancements that could make `envars` even more powerful:
 
+- **Add other Cloud Providers**: Azure etc
 - **AWS Secrets Manager Integration**: Add a new `aws_secrets_manager:` prefix to fetch secrets directly from AWS Secrets Manager, which is a more feature-rich service for managing sensitive data than SSM Parameter Store.
 - **Terraform State File Lookup**: Implement a `terraform_state:` prefix to read outputs directly from a Terraform state file (e.g., from an S3 or GCS backend). This would create a powerful, direct link between your infrastructure-as-code and application configuration.
 - **HashiCorp Vault Integration**: Support for `vault:` lookups to fetch secrets from a HashiCorp Vault instance, which would make `envars` more useful in on-premise or multi-cloud environments.