Add a resolv.conf configuration handler
Bug #1100434 reported by
Craig Tracey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Fix Released
|
Medium
|
Craig Tracey | ||
Bug Description
Managing resolv.conf can be quite handy when running in an environment where you would like to control DNS resolution, despite being provided DNS server information via DHCP. This module will allow one to define the structure of their resolv.conf and write it PER_ONCE.
This is an enhancement request.
Related branches
lp:~craigtracey/cloud-init/resolv-conf-config
- Joshua Harlow (community): Needs Fixing
-
Diff: 180 lines (+166/-0)3 files modifiedcloudinit/config/cc_resolv_conf.py (+107/-0)
doc/examples/cloud-config-resolv-conf.txt (+20/-0)
templates/resolv.conf.tmpl (+39/-0)
| Changed in cloud-init: | |
| assignee: | nobody → Craig Tracey (craigtracey) |
Revision history for this message
| Craig Tracey (craigtracey) wrote | #1 |
| Changed in cloud-init: | |
| status: | New → Fix Committed |
Revision history for this message
| Scott Moser (smoser) wrote | #2 |
| Changed in cloud-init: | |
| importance: | Undecided → Medium |
Revision history for this message
| Scott Moser (smoser) wrote | #3 |
| Changed in cloud-init: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| James Falcon (falcojr) wrote | #4 |
To post a comment you must log in.
Fix committed in 769