[GitHub] [trafficcontrol] jpappa200 opened a new issue, #7232: t3c doesn't add multiple purge_allow_ip parameters to ip_allow.yaml

[GitBox <gi...@apache.org>]

jpappa200 opened a new issue, #7232:
URL: https://github.com/apache/trafficcontrol/issues/7232

   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
   the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request)
   or the Traffic Control Users mailing list (send an email to users-subscribe@trafficcontrol.apache.org to subscribe).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
       * https://github.com/apache/trafficcontrol/issues
       * https://github.com/apache/trafficcontrol/pulls
   -->
   
   <!-- Do not submit security vulnerabilities or support requests here - see above -->
   ## This Bug Report affects these Traffic Control components:
   <!-- delete all those that don't apply -->
   - Traffic Control Cache Config (`t3c`, formerly ORT)
   
   ## Current behavior:
   <!-- Describe how the bug happens -->
   Because of layered profiles a parameter that has the same name and config file only the last parameter is used. That becomes an issue with building ip_allow.yaml file. we have several ip's all in separate parameters to allow purge from each traffic ops host. only one is being added on each run of t3c. Also it's always different so each run of t3c causes a config reload because of a change to ip_allow.yaml. In addition the purge_allow_ip ends up different on all edges which would make it difficult to do a purge if needed.
   
   ## Expected behavior:
   <!-- Describe what the behavior would be without the bug -->
   We need a way to add multiple ip addresses to allow purge and also keep the file from always being different on each run of t3c, and keep the IPs consistent on each edge. 
   
   ## Steps to reproduce:
   <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and
   include the applicable TC version.
   -->
   in the current version of t3c queue updates and run t3c. the ip_allow.yaml file will always come up different. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [trafficcontrol] ocket8888 closed issue #7232: t3c doesn't add multiple purge_allow_ip parameters to ip_allow.yaml

[GitBox <gi...@apache.org>]

ocket8888 closed issue #7232: t3c doesn't add multiple purge_allow_ip parameters to ip_allow.yaml
URL: https://github.com/apache/trafficcontrol/issues/7232


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org