Conversation
|
@jmcx I could use a second pair of eyes before merging this. Could you install from |
|
Works for me, and I really like this UX! One thing we could (in the future perhaps) do is to prompt for confirmation when deleting the broker, especially when it has components attached, for those learning and that don't know that it will delete all related context. Not a new topic, already existed before. In terms of release, this is a fairly disruptive change, but IMO we have more to gain from it in the future than we'll lose from it in terms of disruption, so I would go for it. |
jmcx
left a comment
There was a problem hiding this comment.
let us know soon if this goes into 1.25 so we can make the change known in the blog and release notes. also will require some docs updates but I might not be able to do them in time, you might need to sync with Sameer tomorrow.
6d8157c to
ee05cce
Compare
tmctl deletecommand, now being consistent with thecreateformat, expects the component's kind and name args to execute the deletion, e.g.:tmctl delete source foo tmctl delete transformation bar tmctl delete broker bazetc.