Skip to content
Snippets Groups Projects
  • Simon McVittie's avatar
    feb92d87
    pressure-vessel: Remove the concept of "locking" environment variables · feb92d87
    Simon McVittie authored
    
    This was only necessary because we were reusing a single container
    across multiple entry-point invocations, and expecting "most" arbitrary
    environment variables from each new invocation to be taken into account
    for commands running in the container, which meant that we needed to
    keep track of which environment variables had to be exceptions to that
    rule for technical reasons. Now that we're no longer injecting multiple
    commands into the same container like that, we don't need this
    complexity.
    
    Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
    feb92d87
    History
    pressure-vessel: Remove the concept of "locking" environment variables
    Simon McVittie authored
    
    This was only necessary because we were reusing a single container
    across multiple entry-point invocations, and expecting "most" arbitrary
    environment variables from each new invocation to be taken into account
    for commands running in the container, which meant that we needed to
    keep track of which environment variables had to be exceptions to that
    rule for technical reasons. Now that we're no longer injecting multiple
    commands into the same container like that, we don't need this
    complexity.
    
    Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>