File Resolver
A Sceptre resolver to get file contents. The returned value can be
passed into a parameter as a string, json, or yaml object. The
file extension determines the return type. By default, contents from
any files that do not end in .json or .yaml will be passed in as
a string.
Motivation
Unlike the file_contents resolver which can only pass strings to parameters this resolver can also pass file content in as json and yaml object. This resolver can also resolve remote file contents from the web.
Syntax
parameters|sceptre_user_data:
<name>: !file /path/to/local/file
parameters|sceptre_user_data:
<name>: !file URL/To/File
Examples
Local file
text
Get file content and pass it to the parameter as a text string:
tags/departments.txt
"HR, Governance, Engineering, Marketing"
parameters:
departments: !file tags/departments.txt
json
Get file contents and pass it to the parameter as a json object:
tags/departments.json
[
"HR",
"Governance",
"Engineering",
"Marketing"
]
parameters:
departments: !file tags/departments.json
yaml
Get file contents and pass it to the sceptre_user_data as a yaml object:
tags/departments.yaml
- "HR"
- "Governance"
- "Engineering"
- "Marketing"
sceptre_user_data:
departments: !file tags/departments.yaml
Note: will do the same for files with .yml extension.
Remote file
Works similarly to local file except this will get file contents from the web.
URL
Get file contents from a URL reference:
sceptre_user_data:
departments: !file https://my-bucket.s3.us-east-1.amazonaws.com/tags/departments.json
Metadata
Release files for sceptre-file-resolver 1.0.6
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 | |
|---|---|---|---|---|
| sceptre-file-resolver-1.0.6.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sceptre_file_resolver-1.0.6-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 11.2 kB
Release files / sceptre-file-resolver-1.0.6.tar.gz
| Download URL | sceptre-file-resolver-1.0.6.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d47cfe32d141fb46467fcd319bf4386f0178cf0c2211c6f1d2dffbc80d785a6d
|
|
BLAKE2b-256 checksum How to use checksums |
3620c8162b958668c741bef1d7d247a78f796b705ed0eec72501ef308110923b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.8
|
Release files / sceptre_file_resolver-1.0.6-py2.py3-none-any.whl
| Download URL | sceptre_file_resolver-1.0.6-py2.py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
bba0465a90681ea1d45260c86c3feaf583469f7ddc07e0cd97edcbbb96b459ce
|
|
BLAKE2b-256 checksum How to use checksums |
7d70174f2395655d7736219645182f894bba9c43c7cc97cec540ac3e230b46b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.8
|
Security for sceptre-file-resolver 1.0.6
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.