Add check whether Crostini container is already configured
Adds check whether Crostini container is already configured, so that default Crostini container configuration is triggered only when default Crostini container is not yet successfully configured using currently set CrostiniAnsiblePlaybook policy. Before this CL: container is reconfigured each time container is started if policy is specified & feature flag is set. TEST: unit_tests --gtest_filter="*Ansible*" Bug: 1024859 Change-Id: If1dc83a8130d35a9aa4eba5c8f5e8b39ea1e0dbf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000701 Commit-Queue: Olya Kalitova <okalitova@chromium.org> Reviewed-by:Nic Hollingum <hollingum@google.com> Reviewed-by:
Nikita Podguzov <nikitapodguzov@chromium.org> Cr-Commit-Position: refs/heads/master@{#732810}
Showing
Please register or sign in to comment