You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use "cf app app-name-1 xxxx" or "cf delete app-name-1 yyyy", cf will ignore all the "xxxx/yyyy" things, no warning or error, and the behavior is the same as using "cf app/delete app-name-1".
We have fixed it internally by not allowing user to input more than one parameter. But I wonder if it is better to let the two commands accept more than one app-names, then cf-cli can show multiple apps' info or delete multiple apps at one time.
The text was updated successfully, but these errors were encountered:
@liuhewei - Would you expect a list of apps to be treated atomically? So that if you tried to delete four apps at once (cf delete app1 app2 app3 apt4) but you typo'd app4, would you expect the entire operation to roll back or would you expect three apps to be deleted and an error on the forth attempt?
@goehmen Atomic operation is not necessary, right? I think we can deal with apps one by one, which is easier to be handled and understood. In your example, deleting app1/2/3 successfully until app4, we just need show 3 success and 1 failure logs in console. It's more like a batch processing, just like running the testing cases.
Anyway, currently "cf app/delete" just ignores the inputs after the first app, that I think is not good. Prompting the warning/error for inputting more than one app, or supporting app list is better in my opinion.
When we use "cf app app-name-1 xxxx" or "cf delete app-name-1 yyyy", cf will ignore all the "xxxx/yyyy" things, no warning or error, and the behavior is the same as using "cf app/delete app-name-1".
We have fixed it internally by not allowing user to input more than one parameter. But I wonder if it is better to let the two commands accept more than one app-names, then cf-cli can show multiple apps' info or delete multiple apps at one time.
The text was updated successfully, but these errors were encountered: