Use global variables for domains, TCP ports and eventual shared configurations #4

Closed
opened 2020-04-30 14:21:15 +00:00 by caskd · 1 comment
Owner

Deploying using a global variable configuration allows multiple services to have information about eachother without explicitly including the other service's variables file.

Example uses:
HAProxy configuration generation based on entries
Unbound (and eventually NSD) configuration generation
Proxy white-/blacklist

Deploying using a global variable configuration allows multiple services to have information about eachother without explicitly including the other service's variables file. **Example uses:** HAProxy configuration generation based on entries Unbound (and eventually NSD) configuration generation Proxy white-/blacklist
caskd added this to the Deployment to production milestone 2020-04-30 14:21:15 +00:00
caskd self-assigned this 2020-04-30 14:21:15 +00:00
Author
Owner

Done in 1a4815b496

Done in https://git.redxen.eu/RedXen/ansible/commit/1a4815b49697fe4d5553e287c3e0daa9591211e1
caskd closed this issue 2020-05-14 11:46:35 +00:00
This repo is archived. You cannot comment on issues.
No Label
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: RedXen/ansible#4
No description provided.