Skip to content

confusing behavior att init --contract #1694

@migmartri

Description

@migmartri

when you run for example chainloop att init --workflow my-wf --contract my-contract ... what happens is

1 - a new workflow called my-wf is created (if it doesn't exist) associated with the contract my-contract
2 - a new run is performed

This means that if you after the first run, you provide another contract name chainloop att init --workflow my-wf --contract contract-2, the first contract (my-contract will be used, in other words, the provided contract-2 will be ignored, which was reported as unexpected behavior

Metadata

Metadata

Assignees

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