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.
This is currently still work in progress.
This PR will introduce a simple variable (nested dictionary) to define the zone hierarchy.
The corresponding action plugin creates the zones and endpoints for each host according to the variable.
Each host will only know those zones and endpoints it has to know.
Example:
From this, the plugin will create zones and endpoints based on available variables.
It only returns information. Using the information is still up to the role!
Feedback
There is still a need for a proper way to define variables which will be used for the endpoints
host
attribute.2 hosts could have the same parent but in different networks (2 firewall zones for example).
We must be able to provide some kind of mapping to tell a given host the correct address when it wants to access its parent.
If B wants to access A, it needs IP-1.
If C wants to access A, it needs IP-2.
This mapping must be defined somewhere.
As a fallback, we can always use
inventory_hostname
.