This project has been archived by its maintainers, and is no longer receiving any updates.
AWS Deadline Cloud for Rhino
Disclaimer
This GitHub repository is an example integration with AWS Deadline Cloud that is intended to only be used for testing and is subject to change. This code is an alpha release. It is not a commercial release and may contain bugs, errors, defects, or harmful components. Accordingly, the code in this repository is provided as-is. Use within a production environment is at your own risk!
Our focus is to explore a variety of software applications to ensure we have good coverage across common workflows. We prioritized making this example available earlier to users rather than being feature complete.
This example has been used by at least one internal or external development team to create a series of jobs that successfully rendered. However, your mileage may vary. If you have questions or issues with this example, please start a discussion or cut an issue.
AWS Deadline Cloud for Rhino is a python package that allows users to create AWS Deadline Cloud jobs from within Rhino.
Compatibility
This library requires:
- Rhino 8,
- Python 3.9 or higher; and
- Windows or a macOS operating system.
Submitter
This package provides a python based Rhino plugin that creates jobs for AWS Deadline Cloud using the AWS Deadline Cloud client library. Based on the loaded project it determines the files required, allows the user to specify render options, and builds an OpenJD template that defines the workflow.
Getting Started
Instructions on how to use the submitter in Rhino can be found in Submitter Development Workflow
Versioning
This package's version follows Semantic Versioning 2.0, but is still considered to be in its initial development, thus backwards incompatible versions are denoted by minor version bumps. To help illustrate how versions will increment during this initial development stage, they are described below:
- The MAJOR version is currently 0, indicating initial development.
- The MINOR version is currently incremented when backwards incompatible changes are introduced to the public API.
- The PATCH version is currently incremented when bug fixes or backwards compatible changes are introduced to the public API.
Security
See CONTRIBUTING for more information.
Telemetry
See telemetry for more information.
License
This project is licensed under the Apache-2.0 License.
Release files for deadline-cloud-for-rhino 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| deadline_cloud_for_rhino-0.1.4.tar.gz | 12.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deadline_cloud_for_rhino-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.2 kB
Release files / deadline_cloud_for_rhino-0.1.4.tar.gz
| Download URL | deadline_cloud_for_rhino-0.1.4.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67dfeed8d003a50b4ce49a341a99e821633334586aff06d6f226f53262d2f737
|
|
BLAKE2b-256 checksum How to use checksums |
3c6ec99610cfc9da322b52a1471a538e73ac3a5ab4ca731889582bab9fcd0465
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2024.
Transparency logRelease files / deadline_cloud_for_rhino-0.1.4-py3-none-any.whl
| Download URL | deadline_cloud_for_rhino-0.1.4-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e48ec1f9a8bd4dae0ce94c8c9658af43ef7b87adbfadd5971155b7c3782f4470
|
|
BLAKE2b-256 checksum How to use checksums |
907ccf5cf8e0ab61af76f47f44bf181e704bb9d3f31e8584448c202777df4fe3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2024.
Transparency log