Class BundlingOptions.Builder

java.lang.Object
software.amazon.awscdk.services.lambda.python.BundlingOptions.Builder
All Implemented Interfaces:
software.amazon.jsii.Builder<BundlingOptions>
Enclosing interface:
BundlingOptions

@Stability(Experimental) public static final class BundlingOptions.Builder extends Object implements software.amazon.jsii.Builder<BundlingOptions>
A builder for BundlingOptions
  • Constructor Details

    • Builder

      public Builder()
  • Method Details

    • assetHash

      @Stability(Experimental) public BundlingOptions.Builder assetHash(String assetHash)
      Parameters:
      assetHash - Specify a custom hash for this asset. 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.

      Returns:
      this
    • assetHashType

      @Stability(Experimental) public BundlingOptions.Builder assetHashType(AssetHashType assetHashType)
      Parameters:
      assetHashType - Determines how asset hash is calculated. Assets will get rebuild and uploaded only if their hash has changed. If asset hash is set to SOURCE (default), then only changes to the source directory will cause the asset to rebuild. This means, for example, that in order to pick up a new dependency version, a change must be made to the source tree. Ideally, this can be implemented by including a dependency lockfile in your source tree or using fixed dependencies.

      If the asset hash is set to OUTPUT, the hash is calculated after bundling. This means that any change in the output will cause the asset to be invalidated and uploaded. Bear in mind that pip adds timestamps to dependencies it installs, which implies that in this mode Python bundles will always get rebuild and uploaded. Normally this is an anti-pattern since build

      Returns:
      this
    • buildArgs

      @Stability(Experimental) public BundlingOptions.Builder buildArgs(Map<String,String> buildArgs)
      Parameters:
      buildArgs - Optional build arguments to pass to the default container. This can be used to customize the index URLs used for installing dependencies. This is not used if a custom image is provided.
      Returns:
      this
    • environment

      @Stability(Experimental) public BundlingOptions.Builder environment(Map<String,String> environment)
      Parameters:
      environment - Environment variables defined when bundling runs.
      Returns:
      this
    • image

      @Stability(Experimental) public BundlingOptions.Builder image(DockerImage image)
      Sets the value of BundlingOptions.getImage()
      Parameters:
      image - Docker image to use for bundling. If no options are provided, the default bundling image will be used. Dependencies will be installed using the default packaging commands and copied over from into the Lambda asset.
      Returns:
      this
    • outputPathSuffix

      @Stability(Experimental) public BundlingOptions.Builder outputPathSuffix(String outputPathSuffix)
      Parameters:
      outputPathSuffix - Output path suffix: the suffix for the directory into which the bundled output is written.
      Returns:
      this
    • build

      @Stability(Experimental) public BundlingOptions build()
      Builds the configured instance.
      Specified by:
      build in interface software.amazon.jsii.Builder<BundlingOptions>
      Returns:
      a new instance of BundlingOptions
      Throws:
      NullPointerException - if any required attribute was not provided