On Fri, Aug 17, 2018 at 07:45:12AM -0400, Jason Lixfeld wrote: > Maybe I’m missing an implied exception, but every once in a while one > needs to make some sort of manual configuration to resolve a time > sensitive some corner case that the provisioning system doesn’t > support because someone external to you (ie: customer, IXP > participant) changed something. How is that handled in this use case?
Yes, one should create a mechanism that somewhere in the pipeline you can override configuration the system generated. We call these overrides 'hacks'. We track hacks in a version controlled repository, and I'd like to suggest they should be used sparingly. Kind regards, Job _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
