You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd like to deploy this capability, but our organization has strict object naming conventions. So we'd like to be able to use this functionality with a Lambda that is named differently than "RunNotebook."
I know I can update the cloudformation-base.yml to change the Lambda name that is created by CloudFormation. And I see the Lambda name in the run_notebook.py file. But how do I re-build/re-package the extension after forking the repo?
As an alternative, it would be nice if the name of the Lambda was somehow configurable upon installation of the package/extension.
The text was updated successfully, but these errors were encountered:
We'd like to deploy this capability, but our organization has strict object naming conventions. So we'd like to be able to use this functionality with a Lambda that is named differently than "RunNotebook."
I know I can update the cloudformation-base.yml to change the Lambda name that is created by CloudFormation. And I see the Lambda name in the run_notebook.py file. But how do I re-build/re-package the extension after forking the repo?
As an alternative, it would be nice if the name of the Lambda was somehow configurable upon installation of the package/extension.
The text was updated successfully, but these errors were encountered: