| > I see the claim of saving everything on the filesystem and collaboration via git. yes, ALL IN on git :) based collaboration > Is there a way to handle secrets outside of this flow? Check: https://docs.usebruno.com/secrets-management/overview.html Two ways of handling secrets. > collection A sets a variable, collection B uses it. In bruno collection is the first class citizen, environments reside inside a collection. There is plan to support global environments for the use case you mentioned. > moving requests in a collection via drag/drop isn't obvious and it's actually a pain if you're trying to replace the top item. yes, this ux needs to be improved and there is a bug in drag and drop which should be fixed. |
I'm guessing your recommendation for dealing with separate environments (dev/qa/etc) would then be a single collection with folders underneath and environments defined w/i that collection.
In that sense collections for bruno seem to be more akin to "projects" and are not really equivalent to postman collections in that sense.
That's workable, it good to know the environments are collection specific rather than global.