Previously, without providing config file with --config argument, lambda-uploader would look for the config file in the directory where it was executed, not the function directory.
This behavior is not clearly stated in the README. The example also stores the config file and function in the same directory. Calling lambda-uploader from the root directory of the repository - lambda-uploader example - will raise an exception "lambda.json not a valid configuration file". Moreover, the if condition _load_config in Config._load_config can never be true because the default for the --config argument is 'lamba.json'.
This commit modifies the default config location to "function directory/lambda.json" to follow the expected behavior.
Previously, without providing config file with --config argument, lambda-uploader would look for the config file in the directory where it was executed, not the function directory.
This behavior is not clearly stated in the README. The example also stores the config file and function in the same directory. Calling lambda-uploader from the root directory of the repository -
lambda-uploader example- will raise an exception "lambda.json not a valid configuration file". Moreover, the if condition_load_configinConfig._load_configcan never be true because the default for the --config argument is 'lamba.json'.This commit modifies the default config location to "function directory/lambda.json" to follow the expected behavior.