Building for the Splunk Platform

Template inheritance in Splunk Django not working in Production

faguilar
Path Finder

Hi,

I'm having some trouble with the Django inheritance on my test/production environment Splunk instances. I'm using Splunk 6.3.1 with a 3 SHs cluster architecture.
I have a base_app defined with all the styles and dashboards, and my_app which inherits some of the code of the base_app.

Within django/base_app/templates/configuration_panels i have an html with a table, called riesgo.html, which draws a table with background colors.
I have the same structure in django/my_app/templates/configuration_panels with the file riesgo.html too wich draws a table without background colors.

The problem here and the weird thing is that, having the same files (for both the base_app and my_app) in the testing environment and in production, Splunk is drawing the my_app/riesgo.html (one without background colors) file. And, with THE SAME files in production, Splunk is, however, drawing the base_app/riesgo.html (the one with background colors) file.

My question here is: why is happening that? Is there an explicit way to tell Splunk's Django to use the son's file instead of the parent's?
I don't understand why, if I'm uploading THE SAME repository in test and pro, in test uses the "good" file and in pro uses the paren'ts base file.

Thank you very much.

Regards.

0 Karma
Get Updates on the Splunk Community!

Splunk Training for All: Meet Aspiring Cybersecurity Analyst, Marc Alicea

Splunk Education believes in the value of training and certification in today’s rapidly-changing data-driven ...

Investigate Security and Threat Detection with VirusTotal and Splunk Integration

As security threats and their complexities surge, security analysts deal with increased challenges and ...

Observability Highlights | January 2023 Newsletter

 January 2023New Product Releases Splunk Network Explorer for Infrastructure MonitoringSplunk unveils Network ...