InitFileAssetOptions¶
-
class
aws_cdk.aws_ec2.
InitFileAssetOptions
(*, base64_encoded=None, group=None, mode=None, owner=None, service_restart_handles=None, exclude=None, follow=None, ignore_mode=None, follow_symlinks=None, asset_hash=None, asset_hash_type=None, bundling=None, readers=None, source_hash=None)¶ Bases:
aws_cdk.aws_ec2.InitFileOptions
,aws_cdk.aws_s3_assets.AssetOptions
Additional options for creating an InitFile from an asset.
- Parameters
base64_encoded (
Optional
[bool
]) – True if the inlined content (from a string or file) should be treated as base64 encoded. Only applicable for inlined string and file content. Default: falsegroup (
Optional
[str
]) – The name of the owning group for this file. Not supported for Windows systems. Default: ‘root’mode (
Optional
[str
]) – A six-digit octal value representing the mode for this file. Use the first three digits for symlinks and the last three digits for setting permissions. To create a symlink, specify 120xxx, where xxx defines the permissions of the target file. To specify permissions for a file, use the last three digits, such as 000644. Not supported for Windows systems. Default: ‘000644’owner (
Optional
[str
]) – The name of the owning user for this file. Not supported for Windows systems. Default: ‘root’service_restart_handles (
Optional
[Sequence
[InitServiceRestartHandle
]]) – Restart the given service after this file has been written. Default: - Do not restart any serviceexclude (
Optional
[Sequence
[str
]]) – Glob patterns to exclude from the copy. Default: - nothing is excludedfollow (
Optional
[FollowMode
]) – (deprecated) A strategy for how to handle symlinks. Default: Neverignore_mode (
Optional
[IgnoreMode
]) – The ignore behavior to use for exclude patterns. Default: IgnoreMode.GLOBfollow_symlinks (
Optional
[SymlinkFollowMode
]) – A strategy for how to handle symlinks. Default: SymlinkFollowMode.NEVERasset_hash (
Optional
[str
]) – Specify a custom hash for this asset. IfassetHashType
is set it must be set toAssetHashType.CUSTOM
. For consistency, this custom hash will be SHA256 hashed and encoded as hex. The resulting hash will be the asset hash. 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. Default: - based onassetHashType
asset_hash_type (
Optional
[AssetHashType
]) – Specifies the type of hash to calculate for this asset. IfassetHash
is configured, this option must beundefined
orAssetHashType.CUSTOM
. Default: - the default isAssetHashType.SOURCE
, but ifassetHash
is explicitly specified this value defaults toAssetHashType.CUSTOM
.bundling (
Optional
[BundlingOptions
]) – (experimental) 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/asset-output
. The content at/asset-output
will be zipped and used as the final asset. 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 otherwisereaders (
Optional
[Sequence
[IGrantable
]]) – (experimental) A list of principals that should be able to read this asset from S3. You can useasset.grantRead(principal)
to grant read permissions later. Default: - No principals that can read file asset.source_hash (
Optional
[str
]) – (deprecated) Custom hash to use when identifying the specific version of the asset. For consistency, this custom hash will be SHA256 hashed and encoded as hex. The resulting hash will be the asset hash. NOTE: the source 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 source hash, you will need to make sure it is updated every time the source changes, or otherwise it is possible that some deployments will not be invalidated. Default: - automatically calculate source hash based on the contents of the source file or directory.
Attributes
-
asset_hash
¶ Specify a custom hash for this asset.
If
assetHashType
is set it must be set toAssetHashType.CUSTOM
. For consistency, this custom hash will be SHA256 hashed and encoded as hex. The resulting hash will be the asset hash.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.
- Default
based on
assetHashType
- Return type
Optional
[str
]
-
asset_hash_type
¶ Specifies the type of hash to calculate for this asset.
If
assetHash
is configured, this option must beundefined
orAssetHashType.CUSTOM
.- Default
the default is
AssetHashType.SOURCE
, but ifassetHash
is
explicitly specified this value defaults to
AssetHashType.CUSTOM
.- Return type
Optional
[AssetHashType
]
-
base64_encoded
¶ True if the inlined content (from a string or file) should be treated as base64 encoded.
Only applicable for inlined string and file content.
- Default
false
- Return type
Optional
[bool
]
-
bundling
¶ (experimental) 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/asset-output
. The content at/asset-output
will be zipped and used as the final asset.- 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
- Stability
experimental
- Return type
Optional
[BundlingOptions
]
-
exclude
¶ Glob patterns to exclude from the copy.
- Default
nothing is excluded
- Return type
Optional
[List
[str
]]
-
follow
¶ (deprecated) A strategy for how to handle symlinks.
- Default
Never
- Deprecated
use
followSymlinks
instead- Stability
deprecated
- Return type
Optional
[FollowMode
]
-
follow_symlinks
¶ A strategy for how to handle symlinks.
- Default
SymlinkFollowMode.NEVER
- Return type
Optional
[SymlinkFollowMode
]
-
group
¶ The name of the owning group for this file.
Not supported for Windows systems.
- Default
‘root’
- Return type
Optional
[str
]
-
ignore_mode
¶ The ignore behavior to use for exclude patterns.
- Default
IgnoreMode.GLOB
- Return type
Optional
[IgnoreMode
]
-
mode
¶ A six-digit octal value representing the mode for this file.
Use the first three digits for symlinks and the last three digits for setting permissions. To create a symlink, specify 120xxx, where xxx defines the permissions of the target file. To specify permissions for a file, use the last three digits, such as 000644.
Not supported for Windows systems.
- Default
‘000644’
- Return type
Optional
[str
]
-
owner
¶ The name of the owning user for this file.
Not supported for Windows systems.
- Default
‘root’
- Return type
Optional
[str
]
-
readers
¶ (experimental) A list of principals that should be able to read this asset from S3.
You can use
asset.grantRead(principal)
to grant read permissions later.- Default
No principals that can read file asset.
- Stability
experimental
- Return type
Optional
[List
[IGrantable
]]
-
service_restart_handles
¶ Restart the given service after this file has been written.
- Default
Do not restart any service
- Return type
Optional
[List
[InitServiceRestartHandle
]]
-
source_hash
¶ (deprecated) Custom hash to use when identifying the specific version of the asset.
For consistency, this custom hash will be SHA256 hashed and encoded as hex. The resulting hash will be the asset hash.
NOTE: the source 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 source hash, you will need to make sure it is updated every time the source changes, or otherwise it is possible that some deployments will not be invalidated.
- Default
automatically calculate source hash based on the contents
of the source file or directory.
- Deprecated
see
assetHash
andassetHashType
- Stability
deprecated
- Return type
Optional
[str
]