cloudy-salesforce 0.2.0__tar.gz

cloudy_salesforce-0.2.0/.cloudy_config.example

@@ -0,0 +1,42 @@
+{
+  "auth": {
+    "default_alias": "prod",
+    "aliases": {
+      "prod": {
+        "type": "basic",
+        "login_url": "https://login.salesforce.com",
+        "credentials": {
+          "username": "SF_USERNAME",
+          "password": "SF_PASSWORD",
+          "security_token": "SF_SECURITY_TOKEN"
+        }
+      },
+      "sandbox": {
+        "type": "basic",
+        "sandbox": true,
+        "credentials": {
+          "username": "SF_USERNAME",
+          "password": "SF_PASSWORD",
+          "security_token": "SF_SECURITY_TOKEN"
+        }
+      },
+      "jwt": {
+        "type": "jwt",
+        "login_url": "https://login.salesforce.com",
+        "credentials": {
+          "client_id": "SF_CLIENT_ID",
+          "username": "SF_USERNAME",
+          "private_key": "SF_PRIVATE_KEY"
+        }
+      },
+      "session": {
+        "type": "session",
+        "credentials": {
+          "access_token": "SF_ACCESS_TOKEN",
+          "instance_url": "SF_INSTANCE_URL"
+        }
+      }
+    }
+  },
+  "sobjects": ["Account", "Contact", "Opportunity"]
+}

cloudy_salesforce-0.2.0/.cursor/skills/ship-pr/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: ship-pr
+description: >-
+  Create a pull request, review and fix issues, merge it, then switch back to
+  main and pull. Use when the user asks to create a PR and merge, ship, close
+  and merge, review then merge, or run this project's ship-pr process.
+---
+
+# Ship PR
+
+End-to-end ship: open a PR, review/fix, merge, return to `main`.
+
+Never merge unless this skill was invoked or the user explicitly asked to merge in this conversation. Opening a PR alone is not permission to merge.
+
+## 1. Create the PR
+
+Use `gh` for all GitHub work. Do not use TodoWrite or Task for this step.
+
+In parallel:
+
+- `git status`
+- `git diff` and `git diff --cached`
+- whether the branch tracks a remote and is up to date
+- `git log` and `git diff [base]...HEAD` (full history since the branch diverged)
+
+Then, in order:
+
+1. Create a branch if needed.
+2. Push with `-u` if the branch is not on the remote.
+3. Create the PR:
+
+```bash
+gh pr create --title "the pr title" --body "$(cat <<'EOF'
+## Summary
+<1-3 bullet points>
+
+## Test plan
+[Checklist of TODOs for testing the pull request...]
+
+EOF
+)"
+```
+
+Return the PR URL.
+
+Do not update git config. Do not force-push to main/master.
+
+## 2. Review and fix
+
+Review the PR diff yourself (not only CI).
+
+Fix real bugs, missing tests, and incorrect docs on the feature branch. Commit and push those fixes. Do not commit secrets.
+
+Leave leftover non-blocking work as GitHub issues. Do not pile follow-ups onto `main`.
+
+## 3. Merge
+
+Confirm the PR is mergeable and CI is green (or the user accepted failing checks).
+
+```bash
+gh pr merge <N> --merge --delete-branch
+```
+
+Use a merge commit unless the repo or human prefers squash/rebase.
+
+## 4. Return to main
+
+Always finish on `main` with a current tree:
+
+```bash
+git checkout main
+git pull
+git fetch --prune
+```
+
+Delete the local feature branch if it still exists.
+
+## Do not
+
+- Merge as part of merely opening a PR
+- Leave the session on the feature branch after merge
+- Commit directly to `main`
+- Start the next issue unless asked

cloudy_salesforce-0.2.0/.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,56 @@
+name: Bug report
+description: Report something that is broken or incorrect
+title: "[Bug]: "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug. Please include enough detail to reproduce the issue.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What went wrong?
+      placeholder: A clear description of the bug.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Minimal steps or code snippet to trigger the issue.
+      placeholder: |
+        1. ...
+        2. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What did you expect to happen instead?
+    validations:
+      required: true
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python version
+      description: e.g. 3.12.4
+      placeholder: "3.12"
+    validations:
+      required: true
+
+  - type: input
+    id: package-version
+    attributes:
+      label: cloudy-salesforce version
+      description: Output of `pip show cloudy-salesforce` or git commit if installed from source.
+      placeholder: "0.1.0"
+    validations:
+      required: true

cloudy_salesforce-0.2.0/.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,34 @@
+name: Feature request
+description: Suggest an improvement or new capability
+title: "[Feature]: "
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Describe the problem you are trying to solve and how you would like cloudy-salesforce to help.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What pain point or gap does this address?
+      placeholder: I want to ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Proposed solution
+      description: How should cloudy-salesforce behave or what API would you expect?
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Other approaches, workarounds, or libraries you considered.
+      placeholder: Optional but helpful.

cloudy_salesforce-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: ruff check cloudy_salesforce tests
+      - run: mypy cloudy_salesforce
+      - run: pytest

cloudy_salesforce-0.2.0/.github/workflows/publish.yml

@@ -0,0 +1,22 @@
+name: Publish
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: pypa/gh-action-pypi-publish@release/v1

cloudy_salesforce-0.2.0/.gitignore

@@ -0,0 +1,166 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# IDE
+.vscode
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.cloudy_config
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

cloudy_salesforce-0.2.0/CHANGELOG.md

@@ -0,0 +1,40 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-08-14
+
+### Added
+
+- Hero README, CI badges, contributing guide, issue templates
+- Fixture-backed example generated sObjects under `examples/generated/`
+- mypy in CI; CLI logging for `cloudy-salesforce generate`
+- `SalesforceClient.from_config()` to build a client from `.cloudy_config` and env vars
+- `cloudy-salesforce init` to scaffold `.cloudy_config` and `.env.example`
+- Typed `insert` / `update` / `upsert` / `delete` from `@sobject` dataclasses
+- `DmlResult` return type for composite DML
+- `SalesforceError` with `error_code` and `status_code` for REST failures
+- JWT bearer and session-token authentication (`JwtBearerAuthentication`, `SessionAuthentication`) with `.cloudy_config` aliases
+- Optional rate-limit retries on HTTP 429 and `REQUEST_LIMIT_EXCEEDED` in `SalesforceClient.request`
+- GitHub Actions Trusted Publisher workflow to publish to PyPI on GitHub release
+
+### Changed
+
+- `SalesforceClient` no longer becomes the default instance on construction; use `default=True` or `set_default_instance()`
+- Ignore local `.cloudy_config` so `init` output is not committed by accident
+- Generated `date` / `datetime` fields are `datetime.date` / `datetime.datetime` instead of `str` (regenerate sObjects to pick this up)
+
+## [0.1.0] - 2026-08-14
+
+### Added
+
+- Typed Salesforce client: username/password SOAP auth, SOQL with pagination and `parse_as`, composite CRUD, describe-driven dataclass codegen
+
+[Unreleased]: https://github.com/fishygeek91/cloudy-salesforce/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/fishygeek91/cloudy-salesforce/compare/v0.1.0...v0.2.0
+[0.1.0]: https://github.com/fishygeek91/cloudy-salesforce/releases/tag/v0.1.0

cloudy_salesforce-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing
+
+Thanks for helping improve [cloudy-salesforce](https://github.com/fishygeek91/cloudy-salesforce).
+
+## Development setup
+
+- **Python 3.10+** is required.
+- Install the package and dev dependencies:
+
+  ```bash
+  pip install -e ".[dev]"
+  ```
+
+## Running checks
+
+Run these before opening a pull request:
+
+```bash
+pytest
+ruff check cloudy_salesforce tests
+mypy cloudy_salesforce
+```
+
+Tests use mocks and fixtures. CI and the default test suite do **not** connect to a live Salesforce org.
+
+## Secrets and local config
+
+Do not commit `.env`, `.cloudy_config`, or any credentials. Use environment variables or local config files that stay out of version control.
+
+## Pull requests
+
+- Branch from `main` and open PRs against `main`.
+- Keep changes focused and include tests when behavior changes.
+
+## Code style
+
+- Match patterns in existing modules (typing, naming, structure).
+- Keep tests mocked; avoid requiring a real org unless explicitly documented as an integration test.

cloudy_salesforce-0.2.0/LICENSE

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