Skip to content

Bagger: Use host and bucket from the main configuration in the DART workflow #47

Closed
@zoidy

Description

@zoidy

Is there an existing issue for this?

  • I have searched the existing issues

Description

Currently, DART uploads to the specified host and bucket defined in the workflow file. The config file for bagger also defines the host and bucket for other reason (see the bagger readme file). This is confusing because it would seem that DART should also use the host and bucket specified by the main config (as it does with the Wasabi credentials).

Suggested Implementation

Add a new configuration option to the bagger toml config that specifies whether the DART workflow file should be parsed. If the option is set, the json for the workflow should be parsed to replace the host and bucket with those given in the toml file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions