manage resolv.conf

Registered by Hugh Saunders

There was a situation during an upgrade recently, where it was necessary to manage the resolv.conf on all the containers in the infrastructure.

I wrote a very simple bespoke role to drop in the appropriate template. However it may be useful to have an optional play/role for if this situation recurs.

I'm not sure if this an extras repo thing or os-ansible-deployment.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Not
Drafter:
Hugh Saunders
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Kevin Carter

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.