from top of my head we have two options once you run att init after the workflow was created

1 - if the contract you provide with the flag --contract is different than the one from the existing workflow fail the attestation telling the user to change it or
2 - if you provide --contract, make sure to swap it if needed.

I am leaning towards 2, wdyt @jiparis @javirln

I would say option 2 is more user friendly as long as we always inform the end user about that swap!

2. is too much a side effect in my opinion. Could we just warn the user that --contract will be ignored if the workflow already exists? Another option is to change the option to something more meaningful for this specific case, like --initial-contract or similar

@jiparis did we end up implementing this? I remember we talked about it

In any case I've tried it like this as part of the quickstart and didn't work

 chainloop att init \
  --workflow mywf \
  --project myproject \
  --contract https://raw.githubusercontent.com/chainloop-dev/chainloop/refs/heads/main/docs/examples/quickstart/quickstart-contract.yaml --replace

It was implemented here #1902. What's the error?

It was implemented here #1902. What's the error?

not an error, but instead that I can't see it updating the contract.

@jiparis it would be nice if you could give it a check to see if we can close this

Sure, att init never updates the contract, that's the confusing part. I'll take a look

Sure, att init never updates the contract, that's the confusing part. I'll take a look

oh, so we didn't add it in the end I guess?

Please check #1974, this should fix it.