Hide traceback in rendered config

[alehaa]

NetBox version

v4.1.6

Feature type

Change to existing functionality

Triage priority

I volunteer to perform this work (if approved)

Proposed functionality

When a rendered configuration template raises an exception, the full traceback is included in the Rendered Config pane. I suggest limiting this to the exception type and message.

Use case

End users without a programming background might be confused by seeing the full traceback. Seeing only the error message may be more helpful to them for resolving the problem.

Database changes

None.

External dependencies

None.

[bctiemann]

Seems reasonable. It might be helpful if you could include a screenshot of the current behavior in the issue description so we can evaluate the before/after UX.

[sdktr]

What if you actually want to see the full traceback to fix/better understand the issue?

[alehaa]

@sdktr As far as I know, the traceback doesn't contain any useful information for tracing problems inside the template. Instead, it contains the call stack of how the template is rendered. So I've created a PR to limit that information, as it's usually not helpful to non-dev users at all.

I see the benefit of adding information about where a template error occurs. However, as far as I know, only the TemplateSyntaxError exception provides additional information such as line numbers. If you have suggestions for tweaking the error message to make it more useful, feel free to comment my PR and I'll see if I can integrate it.