Hi @Amanda Wee - I think the confusion originates from the generic name of the flow in the top example; the flow name in that case is
"s3-flow"
which is the slugified-flow-name but I definitely can see where that causes confusion; if you’d like to PR a name change to that example we’d definitely accept it!
a
Amanda Wee
01/12/2021, 4:37 AM
Also, the latter docs state:
Copy code
Flows registered with this Storage option will automatically be labeled with s3-flow-storage.
but from what I see, this isn't happening: my flows have no label at all
Amanda Wee
01/12/2021, 4:38 AM
@Chris White yeah, that makes sense. Would be better to be consistent with the latter doc as that's more obviously metasyntatic.
c
Chris White
01/12/2021, 4:38 AM
ah yes that behavior changed very recently with 0.14.0 so we should update that
Chris White
01/12/2021, 4:38 AM
@Marvin open “Storage label documentation updates”
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.