Skip to content

Document Migration from upload_lambda_functions to PythonFunction Hook #2853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

RepoBirdBot
Copy link

This PR updates the documentation to assist users in migrating from the deprecated runway.cfngin.hooks.aws_lambda.upload_lambda_functions hook to the new runway.cfngin.hooks.awslambda.PythonFunction hook. The changes include:

  • A detailed explanation of the functional differences between the old and new hooks.
  • Key configuration changes, including updated argument mappings such as:
    • args.bucketargs.bucket_name
    • args.prefixargs.object_prefix
    • args.functions.<func_name>.pathargs.source_code
    • args.functions.<func_name>.runtimeargs.runtime
  • Guidance on handling Dockerization changes with clear instructions on enabling or disabling Docker builds.
  • Before and after YAML examples to show how a single hook configuration may be split into multiple PythonFunction hook definitions.
  • Updated lookup instructions for accessing hook-generated attributes in your blueprints/templates.

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 📦🐦

…o PythonFunction hook

Add detailed migration instructions from the deprecated upload_lambda_functions hook to the new PythonFunction hook. Include key argument mappings, configuration changes, and examples to assist users in transitioning to the updated hook structure.
@ariel-frischer
Copy link

👋 Hello from RepoBird.ai!

I'm the founder of RepoBird.ai, an AI Software Engineer Agent that integrates seamlessly as a GitHub App.

This Pull Request was automatically generated by our agent, RepoBirdBot, to address issue #2850. This issue was marked as a good first issue and appeared to be unassigned.

Why this PR?

  • We're currently testing RepoBird by offering automated fixes for open-source projects like yours.
  • Our goal is to help maintainers and provide useful contributions.
  • We greatly value feedback from maintainers and early users during this phase.

Your Feedback Matters:

Please review the proposed changes. If this type of automated contribution isn't suitable for your repository, or if this specific PR isn't helpful, just let me know! I'll close it, make any improvements and unlist these PRs – no worries.

Want changes? If you have feedback or requested modifications, please leave comments directly on this PR. Once all review comments are in, comment @RepoBirdBot Update and I will manually run the agent again, taking into account all PR comments and any pipeline failure logs.


Interested in learning more?

Thank you!

@ariel-frischer
Copy link

Darn, unfortunately this automation does not allow changes to branch names but I can always create a new branch + PR if needed to fix branch name pipeline issue. If these changes are no good that is fine you can always close this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants