doover-cli 0.1.0__tar.gz

doover_cli-0.1.0/.github/CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing
+
+Thank you for your interest in contributing to the Doover project! 
+
+We welcome contributions from the community and appreciate your help in making Doover better. Below are some guidelines to help you get started.
+
+## Install Dependencies
+
+To set up your development environment, install the optional dependencies for the CLI:
+
+```bash
+uv sync
+source .venv/bin/activate
+```
+
+## Testing
+
+To run unit tests, use `pytest` in the main directory of the repository:
+
+```bash
+uv run pytest
+```
+
+## Pre-commit Hooks
+
+We use pre-commit hooks to ensure code quality and consistency using Ruff. To set up pre-commit hooks, run the following command:
+
+```bash
+pre-commit install
+```

doover_cli-0.1.0/.github/ISSUE_TEMPLATES/bug-report.yaml

@@ -0,0 +1,42 @@
+name: Bug Report
+description: File a bug report.
+title: "[Bug]: "
+labels: ["bug"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: What version are you running? (use `doover --version`)
+    validations:
+      required: false
+  - type: dropdown
+    id: os-version
+    attributes:
+      label: What OS are you seeing the problem on?
+      multiple: true
+      options:
+        - MacOS
+        - Linux (Parallels)
+        - Linux
+        - Windows
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell

doover_cli-0.1.0/.github/ISSUE_TEMPLATES/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

doover_cli-0.1.0/.github/ISSUE_TEMPLATES/feature-request.yml

@@ -0,0 +1,49 @@
+name: Feature Request
+description: Suggest a feature for this library
+labels: feature request
+body:
+  - type: input
+    attributes:
+      label: Summary
+      description: >
+        A short summary of what your feature request is.
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      multiple: false
+      label: What is the feature request for?
+      options:
+        - The core library
+        - discord.ext.commands
+        - discord.ext.tasks
+        - The documentation
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: The Problem
+      description: >
+        What problem is your feature trying to solve?
+        What becomes easier or possible when this feature is implemented?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: The Ideal Solution
+      description: >
+        What is your ideal solution to the problem?
+        What would you like this feature to do?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: The Current Solution
+      description: >
+        What is the current solution to the problem, if any?
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional Context
+      description: If there is anything else to say, please do so here.

doover_cli-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+## Summary
+
+<!-- What is this pull request for? Does it fix any issues? -->
+
+## Checklist
+
+<!-- Put an x inside [ ] to check it, like so: [x] -->
+
+- [ ] If code changes were made then they have been tested.
+    - [ ] I have updated the documentation to reflect the changes.
+- [ ] This PR fixes an issue.
+- [ ] This PR adds something new (e.g. new method or parameters).
+- [ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
+- [ ] This PR is **not** a code change (e.g. documentation, README, ...)

doover_cli-0.1.0/.github/workflows/lint-test.yml

@@ -0,0 +1,22 @@
+name: Run Linting
+
+on:
+  push:
+
+jobs:
+  run_tests:
+    name: Run Linting
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup UV
+        uses: astral-sh/setup-uv@v6
+        with:
+          python-version: 3.11
+      - uses: astral-sh/ruff-action@v3
+
+      - name: Run Linting
+        run: ruff check --output-format=github
+
+      - name: Run Tests
+        run: uv run pytest tests

doover_cli-0.1.0/.github/workflows/release-pypi.yml

@@ -0,0 +1,35 @@
+name: Push Release to PyPi
+
+on:
+  workflow_dispatch:
+    inputs:
+      confirmation:
+        description: 'I want to manually trigger a PyPi push, without publishing a GitHub release (not recommended!)'
+        required: true
+        type: boolean
+  release:
+    types: [created]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  deploy:
+    name: Upload release to PyPI
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/pydoover
+
+    if: github.event_name != 'workflow_dispatch' || (github.event_name == 'workflow_dispatch' &&  github.event.inputs.confirmation != 'false')
+    steps:
+    - uses: actions/checkout@v4
+    - name: Install UV
+      uses: astral-sh/setup-uv@v6
+      with:
+        python-version: 3.11
+    - name: Build Package
+      run: uv build
+    - name: Publish Package
+      run: uv publish

doover_cli-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,70 @@
+name: Release Package to APT Repository
+
+on:
+  workflow_dispatch:
+    inputs:
+      confirmation:
+        description: 'I want to manually trigger an apt release, without publishing a GitHub release (not recommended!)'
+        required: true
+        type: boolean
+  release:
+    types: [created]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  build:
+    name: Build Debian package
+    runs-on: ubuntu-22.04
+
+    container:
+      image: spaneng/doover-apt-cicd-base:latest
+
+    steps:
+      - name: Configure AWS Credentials
+        uses: aws-actions/configure-aws-credentials@v4
+        with:
+          aws-region: ${{ vars.AWS_DEFAULT_REGION }}
+          role-to-assume: ${{ vars.AWS_APT_DEPLOY_ROLE_ARN }}
+
+      - uses: actions/checkout@v4
+      - name: Install dependencies
+        run: |
+          cd /tmp
+          apt update
+          echo 'y' | mk-build-deps -i ${GITHUB_WORKSPACE}/debian/control
+
+      - name: Build package
+        run: |          
+          git config --global --add safe.directory "$GITHUB_WORKSPACE"
+
+          gbp buildpackage \
+            --git-ignore-branch \
+            --git-upstream-tree=${GITHUB_SHA} \
+            --git-builder="debuild -b -us -uc" \
+            --git-export-dir=debian/build/
+          echo --- debian/build/
+          find debian/build/
+
+      - name: Publish package
+        if: github.event_name != 'workflow_dispatch' || (github.event_name == 'workflow_dispatch' &&  github.event.inputs.confirmation != 'false')
+
+        env:
+          REPO_SIGNING_KEY_ID: ${{ vars.APT_RELEASE_REPO_SIGNING_KEY_ID }}
+          REPO_SIGNING_KEY_PASSPHRASE: ${{ secrets.APT_RELEASE_REPO_SIGNING_KEY_PASSPHRASE }}
+
+        run: |
+          export GPG_TTY=`tty`
+          export PACKAGE_NAME=$(dh_listpackages)
+          aws s3 cp s3://doover-apt-repo-private/apt_gpg_private.backup - | \
+            gpg --import --pinentry-mode=loopback --no-tty --batch --yes --passphrase ${REPO_SIGNING_KEY_PASSPHRASE}
+          aws s3 cp debian/build/*.deb s3://doover-apt-packages/${PACKAGE_NAME}/
+          deb-s3 upload \
+            debian/build/*.deb \
+            --lock \
+            --bucket "apt.u.doover.com" \
+            --s3-region "${AWS_DEFAULT_REGION}" \
+            --sign "${REPO_SIGNING_KEY_ID}" \
+            --gpg-options "\-\-pinentry-mode=loopback \-\-no-tty \-\-batch \-\-yes \-\-passphrase ${REPO_SIGNING_KEY_PASSPHRASE}"

doover_cli-0.1.0/.gitignore

@@ -0,0 +1,129 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+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/
+
+# 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
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.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
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.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/

doover_cli-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+- repo: https://github.com/astral-sh/ruff-pre-commit
+  rev: v0.11.11
+  hooks:
+    - id: ruff-check
+      args: [ --fix ]
+    - id: ruff-format

doover_cli-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [2024-Present] [Doover]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

doover_cli-0.1.0/PKG-INFO

@@ -0,0 +1,13 @@
+Metadata-Version: 2.4
+Name: doover-cli
+Version: 0.1.0
+Summary: CLI for Doover
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: jsf>=0.11.2
+Requires-Dist: paramiko>=3.5.1
+Requires-Dist: pydoover
+Requires-Dist: pytz>=2025.2
+Requires-Dist: requests>=2.32.3
+Requires-Dist: typer==0.15.1
+Requires-Dist: tzlocal>=5.3.1

doover_cli-0.1.0/README.md

@@ -0,0 +1,62 @@
+# Doover APT Package for Doover CLI
+
+This CLI package is the core Doover CLI, allowing you to interact and perform scripting with the Doover platform, 
+generate, test, lint, run and deploy new applications and more.
+
+# Installation
+
+If you don't have `uv` installed, it is suggested to install that first:
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+## With UV / Pip
+
+In order of preference (choose one):
+
+```bash
+uv tool install doover-cli
+```
+
+```bash
+pipx install doover-cli
+```
+
+```bash
+pip install doover-cli
+```
+
+
+## Linux / Debian
+
+Make sure you have the doover apt repository added to your system:
+```bash
+sudo wget http://apt.u.doover.com/install.sh -O - | sh
+```
+
+And then install the package with:
+```bash
+sudo apt install doover-cli
+```
+
+## MacOS / Homebrew
+
+If you don't have `brew` installed, it is suggested to install that first:
+```bash
+```
+
+
+
+# Usage
+
+Invoke the CLI with ...:
+```bash
+doover --help
+```
+
+
+# Contributing
+See [CONTRIBUTING.md](CONTRIBUTING.md) for more information on how to contribute to this project.
+
+# License
+This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.

doover_cli-0.1.0/debian/changelog

@@ -0,0 +1,5 @@
+doover-cli (0.1.0) focal jammy; urgency=medium
+
+  * Initial release of CLI
+
+ -- Joshua Bramley <josh@span-eng.com>  Tue, 26 Nov 2024 12:28:56 +1000