Environment variable file path

Case 1: If the user provided an environment variable file path.

...

Consider this path as example: (lambda-demo/EnvironmentFile/lambda-demo.json)

First, operation will perform validation on a given variable file path, we are throwing an exception if the file extension is not present. [ FDAWS_LAMBDA_00021_ADD_ENV_INVALID_FILE_PATH, "Invalid file path is given, the file extension is not present." ]

...

Artifact File Path ( Applicable only for local archive )

Case 1: If the user provided an Artifact file path.

...

Consider this path as example: ( lambda-demo/FunctionCode/lambda-demo.zip )

• Consider the given path as an absolute path and check if an Artifact file exists on the given path.

• If the file does not exist on the given path, then consider the path as a relative path and check the file in the Artifact directory. ( $FD_ARTIFACT_DIR/lambda-demo/FunctionCode/lambda-demo.zip)

• If no file is found using the above option, then check if the file is present under the temp Directory.

...

After performing the above steps if we don’t get the file on the given path then we are throwing an exception, with the error message: "No zip file is found on given path:"

Case 2: If the user is not provided a path

If the user is not provided a path, then we are searching the Artifact directory for the file with the ‘zip’ extension and using that file to deploy the lambda function. In case more than one file is present we are throwing an exception.

...