Skip to content

setup-data-libraries cannot update a data library without --legacy #15951

@hexylena

Description

@hexylena
setup-data-libraries -i data-library.yaml

image

and

setup-data-libraries -i data-library.yaml --legacy

image

behave quite differently.

I want to use the new batch upload API. It's way faster and the result is much more human friendly. But we are stuck using the --legacy API, because if you run without the --legacy flag, then it creates a duplicate data library.

Having a period of time with a duplicate (or with no) data library is not ideal.

  1. Could the batch upload API update a data library rather than producing a new data lib?
  2. Otherwise, could we get the nicer short names in the --legacy api?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions