CustomCommandOptions Struct
Options for creating AssetCode with a custom command, such as running a buildfile.
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import * as cdk from 'aws-cdk-lib';
import { aws_iam as iam } from 'aws-cdk-lib';
import { aws_lambda as lambda } from 'aws-cdk-lib';
import { aws_kms as interfaces_kms } from 'aws-cdk-lib/interfaces';
declare const commandOptions: any;
declare const dockerImage: cdk.DockerImage;
declare const grantable: iam.IGrantable;
declare const keyRef: interfaces_kms.IKeyRef;
declare const localBundling: cdk.ILocalBundling;
const customCommandOptions: lambda.CustomCommandOptions = {
assetHash: 'assetHash',
assetHashType: cdk.AssetHashType.SOURCE,
bundling: {
image: dockerImage,
// the properties below are optional
bundlingFileAccess: cdk.BundlingFileAccess.VOLUME_COPY,
command: ['command'],
entrypoint: ['entrypoint'],
environment: {
environmentKey: 'environment',
},
local: localBundling,
network: 'network',
outputType: cdk.BundlingOutput.ARCHIVED,
platform: 'platform',
securityOpt: 'securityOpt',
user: 'user',
volumes: [{
containerPath: 'containerPath',
hostPath: 'hostPath',
// the properties below are optional
consistency: cdk.DockerVolumeConsistency.CONSISTENT,
}],
volumesFrom: ['volumesFrom'],
workingDirectory: 'workingDirectory',
},
commandOptions: {
commandOptionsKey: commandOptions,
},
deployTime: false,
displayName: 'displayName',
exclude: ['exclude'],
followSymlinks: cdk.SymlinkFollowMode.NEVER,
ignoreMode: cdk.IgnoreMode.GLOB,
readers: [grantable],
sourceKMSKey: keyRef,
};
Properties
assetHashstringasset_hashstrassetHashStringAssetHashstringAssetHash*string= based on `assetHashType`#notes
If 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 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.
assetHashTypeAssetHashTypeasset_hash_typeAssetHashTypeassetHashTypeAssetHashTypeAssetHashTypeAssetHashTypeAssetHashTypeAssetHashType= the default is `AssetHashType.SO…#If assetHash is configured, this option must be undefined or AssetHashType.CUSTOM.
default
Default: the default is AssetHashType.SOURCE, but if assetHash is explicitly specified this value defaults to AssetHashType.CUSTOM.
bundlingBundlingOptionsbundlingBundlingOptionsbundlingBundlingOptionsBundlingBundlingOptionsBundlingBundlingOptions= uploaded as-is to S3 if the asse…#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
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
commandOptions{ [key: string]: any }command_optionstyping.Mapping[str, Any]commandOptionsMap<String, Object>CommandOptionsIDictionary<string, object>CommandOptions*map[string]interface{}= : see `child_process.SpawnSyncOp…#default
Default: : see child_process.SpawnSyncOptions (https://nodejs.org/api/child_process.html#child_processspawnsynccommand-args-options).
notes
i.e. are copied over to a different location and not needed afterwards. Setting this property to true has an impact on the lifecycle of the asset, because we will assume that it is safe to delete after the CloudFormation deployment succeeds.
For example, Lambda Function assets are copied over to Lambda during deployment. Therefore, it is not necessary to store the asset in S3, so we consider those deployTime assets.
displayNamestringdisplay_namestrdisplayNameStringDisplayNamestringDisplayName*string= Stack-relative construct path#notes
If supplied, the display name will be used in locations where the asset identifier is printed, like in the CLI progress information. If the same asset is added multiple times, the display name of the first occurrence is used.
The default is the construct path of the Asset construct, with respect to the enclosing stack. If the asset is produced by a construct helper function (such as lambda.Code.fromAsset()), this will look like MyFunction/Code.
We use the stack-relative construct path so that in the common case where you have multiple stacks with the same asset, we won't show something like /MyBetaStack/MyFunction/Code when you are actually deploying to production.
excludestring[]excludetyping.List[str]excludeList<String>Excludestring[]Exclude*[]*string= nothing is excluded#See ignoreMode to set the matching behavior. Has no effect on Assets bundled using the bundling property.
followSymlinksSymlinkFollowModefollow_symlinksSymlinkFollowModefollowSymlinksSymlinkFollowModeFollowSymlinksSymlinkFollowModeFollowSymlinksSymlinkFollowMode= SymlinkFollowMode.NEVER#ignoreModeIgnoreModeignore_modeIgnoreModeignoreModeIgnoreModeIgnoreModeIgnoreModeIgnoreModeIgnoreMode= IgnoreMode.GLOB#readersIGrantable[]readerstyping.List[IGrantable]readersList<IGrantable>ReadersIGrantable[]Readers*[]IGrantable= No principals that can read file…#You can use asset.grantRead(principal) to grant read permissions later.
default
Default: No principals that can read file asset.