Skip to content

alias key is inconsistent in openfn.yaml #1403

@josephjclark

Description

@josephjclark

When checking out a project, should alias get written to openfn.yaml? Probably yes - it makes it more clear which project is checked out to workflows, which is important feedback for tooling and users.

At the moment its use seems to be inconsistent. Sometimes its there, sometimes it's not. See this commit where it was removed.

We should think about the project key some more. Should it just be the aliased name of the checked out project? Do we
actually need any of the other metadata in that file? Looking at it right now I don't think so.

This may relate to #1275

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    New Issues

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions