Fix(dhcp_configuration) Per dhcp client registration setting not working #606
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
This fixes the behaviour that the dhcp bootfile-name option is now also rendered on a per client basis instead of only global.
Futher it aligns to the AVD documentation now.
Related Issue(s)
Fixes #605
Component(s) name
arista.cvp.dhcp_configuration
Proposed changes
dhcp.conf.j2 is adjusted:
old:
option bootfile-name "{{ ztp.default.registration }}";
new:
How to test
Use the key
registration
per dhcp client:Checklist
User Checklist
Repository Checklist