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
This may not really be an issue with tweed, and it may have something to do with the way cf works, but I've noticed when you use cf to create a service through tweed (as a service broker), then run cf services, what that reports is out of sync with what tweed ls reports. See screenshot:
As you can see, cf services reports that a given service is still being created, but tweed ls reports the status as "quiet" (which I assume is basically equivalent to "ready"). If you give cf services some additional amount of time (~5 minutes or so?) it eventually catches up to reflect the same status as tweed ls does. Ideally those two things should be in sync at all times.
Just flagging this so it's known; definitely not a high-priority or breaking item at all, and like I said, depending on how much of this behavior is dependent on cf it may not even be something you can address.
The text was updated successfully, but these errors were encountered:
This may not really be an issue with tweed, and it may have something to do with the way cf works, but I've noticed when you use
cf
to create a service through tweed (as a service broker), then runcf services
, what that reports is out of sync with whattweed ls
reports. See screenshot:As you can see,
cf services
reports that a given service is still being created, buttweed ls
reports the status as "quiet" (which I assume is basically equivalent to "ready"). If you givecf services
some additional amount of time (~5 minutes or so?) it eventually catches up to reflect the same status astweed ls
does. Ideally those two things should be in sync at all times.Just flagging this so it's known; definitely not a high-priority or breaking item at all, and like I said, depending on how much of this behavior is dependent on
cf
it may not even be something you can address.The text was updated successfully, but these errors were encountered: