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
{{ message }}
Repository navigation
Commit ee076aa
Browse filesBrowse the repository at this point in the historyBrowse files
OP#10322: Read the prefix from the project, not the environment
The providers now list under the prefix the loaded project declares, and
S3_KEY_PREFIX is gone from the environment. An instance is no longer pinned to
one prefix for its lifetime: opening another project moves where it reads,
within the one bucket it may authenticate to.
With no project loaded there is no prefix and nothing to list, so the time-range
dialog is refused and says to load a project first. That is a behaviour change
to slice 6, which offered the dialog at startup, and matches how the worker
runs: a lease starts when an otconfig is delivered.
The acceptance test preloads a project otconfig instead of setting
S3_KEY_PREFIX, which is the same change seen from the outside.
ADR 0003's variable list is marked as the list at the time of that ADR rather
than rewritten: the decision to configure S3 through the environment stands,
only the prefix left it.
0 commit comments