Document Migration from upload_lambda_functions to PythonFunction Hook #2853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the documentation to assist users in migrating from the deprecated
runway.cfngin.hooks.aws_lambda.upload_lambda_functions
hook to the newrunway.cfngin.hooks.awslambda.PythonFunction
hook. The changes include:args.bucket
→args.bucket_name
args.prefix
→args.object_prefix
args.functions.<func_name>.path
→args.source_code
args.functions.<func_name>.runtime
→args.runtime
PythonFunction
hook definitions.Since the deprecated hook is scheduled for removal in Runway v3.0.0, users should review these changes carefully and update their configurations accordingly. This documentation aims to provide clear, step-by-step guidance to ensure a smooth transition.
Please review and provide feedback if any further clarification or additional examples are needed.
Created with Repobird.ai 📦🐦