bw addresses convention items by the secret name alone, so a second project storing DATABASE_URL overwrites the first project's value and both then read the survivor — against the repo's own fake-bw harness, project B's set issued bw edit item it-project-a carrying project A's id, and project B's get returned project A's value. folder_prefix looks like the intended scope, and its doc comment says it defaults to secretspec/{project}/{profile}, but it is only parsed from ?folder= and echoed back by uri(): setting it changes neither invocation, and created items carry no folderId at all. Happy to put up a fix.
bw addresses convention items by the secret name alone, so a second project storing
DATABASE_URLoverwrites the first project's value and both then read the survivor — against the repo's own fake-bw harness, project B'ssetissuedbw edit item it-project-acarrying project A's id, and project B'sgetreturned project A's value.folder_prefixlooks like the intended scope, and its doc comment says it defaults tosecretspec/{project}/{profile}, but it is only parsed from?folder=and echoed back byuri(): setting it changes neither invocation, and created items carry nofolderIdat all. Happy to put up a fix.