Asset hash options.
|asset||Specify a custom hash for this asset.|
|asset||Specifies the type of hash to calculate for this asset.|
|bundling?||Bundle the asset by executing a command in a Docker container.|
(optional, default: based on
Specify a custom hash for this asset.
assetHashType is set it must
be set to
AssetHashType.CUSTOM. For consistency, this custom hash will
be SHA256 hashed and encoded as hex. The resulting hash will be the asset
NOTE: the hash is used in order to identify a specific revision of the asset, and used for optimizing and caching deployment activities related to this asset such as packaging, uploading to Amazon S3, etc. If you chose to customize the hash, you will need to make sure it is updated every time the asset changes, or otherwise it is possible that some deployments will not be invalidated.
(optional, default: the default is
AssetHashType.SOURCE, but if
explicitly specified this value defaults to
Specifies the type of hash to calculate for this asset.
assetHash is configured, this option must be
(optional, default: uploaded as-is to S3 if the asset is a regular file or a .zip file,
archived into a .zip file and uploaded to S3 otherwise)
Bundle the asset by executing a command in a Docker container.
The asset path will be mounted at
/asset-input. The Docker
container is responsible for putting content at
The content at
/asset-output will be zipped and used as the