Files
Dmitriy Rabotyagov 52c710ae91 Always escalate privileges for attaching to containers
At the moment Ansible will escalate privileges when connecting to
containers when `become: True`. Without escalation attempt to attach
to container is doomed to fail with insufficient privileges.

However, always having become enable will also result in privilege
escalation inside of the container, which might be not anticipated
as that will override `container_user`.

Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-tests/+/925746
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-tests/+/926149
Change-Id: I101b2d0a3d0ac23ea48caadab10303ba20835e9a
2024-08-26 12:40:16 +00:00

20 lines
651 B
YAML

---
# Copyright 2017, Logan Vig <logan2211@gmail.com>
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
bridges:
- "br-mgmt"
ansible_connection: local