Skip to content

feat: support custom output path #9

Open
@pnadolny13

Description

@pnadolny13

Related to slack thread https://meltano.slack.com/archives/CMN8HELB0/p1679141123085079

I see that theres several ways to define the naming conventions of the output files but I dont see a way to set a custom output path directory. The person in slack was confused by the output_path_prefix setting because they expected it to allow a custom output path. Ultimately changing variants to use the destination_path with the hotgluexyz variant solved their problem. Either:

  • document how to pass a custom path with the current configurations
  • implement a way to provide a custom path

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions