example:
pip install appsync-copier
Make a .env file and add
- GRAPHQL_URL
- ACCESS_KEY
- SECRET_KEY
Make a schema.graphql and paste the schema models..
Continue with the following example:
from appsync_copier import AppSyncCopier, AppSyncClient
from dotenv import load_dotenv
import boto3
import os
load_dotenv()
region = boto3.Session().region_name
client = AppSyncClient(os.getenv("GRAPHQL_URL"),
os.getenv("ACCESS_KEY"),
os.getenv("SECRET_KEY"),
region)
copier = AppSyncCopier(
schema_path="schema.graphql",
client=client,
)
copier.copy_model(
"MODEL_NAME",
"MODEL_ID"
)
1 maintainer
Metadata
1 maintainer
Release files for appsync-copier 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| appsync-copier-0.0.3.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| appsync_copier-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.2 kB
Release files / appsync-copier-0.0.3.tar.gz
| Download URL | appsync-copier-0.0.3.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5626912b1edc8a2bf01acd79a7b23936b09e4b12e9b7049a6c557787857ba2f
|
|
BLAKE2b-256 checksum How to use checksums |
47734799fb20fd60897fd8e0874d534e1b1bf6189192921c127aeb443f149789
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / appsync_copier-0.0.3-py3-none-any.whl
| Download URL | appsync_copier-0.0.3-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1664bcf44b65f94cbdfa866da78a350fb8af1d2486e1af8e9bd2614f5193205e
|
|
BLAKE2b-256 checksum How to use checksums |
3c2bfcaf8fc499436e7598def5e6d446a3e23718d8a1524edd940489d686b3ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for appsync-copier 0.0.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
