Skip to content

Wrong imports in routing/other orchestration Lambdas from datalakeLibrary #538

@dlpzx

Description

@dlpzx

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Follow the workshop and deploy an SDLF pipeline and dataset
  2. trigger the pipeline by uploading a file to S3
  3. the routing Lambda in stage A fails with the following error message:
Unable to import module 'lambda_function': No module named 'datalake_library.configuration'

Looking at the Lambda code:

from datalake_library.commons import init_logger
from datalake_library.configuration.resource_configs import StateMachineConfiguration
from datalake_library.interfaces.states_interface import StatesInterface

And then at the datalake_library:

Image

It seems like the PR that removes octagon support #449 also removed the configuration of stateMachines. The configuration is now in datalake_library.sdlf.config and is called with different arguments.

We need to 1. decide what is the support 2. make sure the calls to datalakeLibrary imports are consistent

Expected behavior
The pipeline to be executed correctly and imports from datalakeLibraryLayer to exist as they are called.

Screenshots
If applicable, add screenshots to help explain your problem.

SDLF release (if known): >=2.7.0

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions