Glenn Matthews

In other words, once you begin using this library, you may never change `SECRET_KEY` again, even if you're defining `CRYPTOGRAPHY_KEY` as the documentation recommends.

What data in particular are you looking to include in the export? Is just job/timestamp/user/status sufficient or would you be looking to somehow include the logs as well?

OK, so this is more about exporting the logs for a single JobResult than it is for exporting the overall JobResults table, correct?

Can confirm from code inspection that this looks wrong in dcim.views.PathTraceView: ```python try: path_id = int(request.GET.get("cablepath_id")) #

Plugins can already add new homepage content (https://nautobot.readthedocs.io/en/stable/development/homepage/) and you can use the `HIDE_RESTRICTED_UI` config setting if you want content that a user doesn't have access to to be removed...

Can you clarify what you mean by "actual state" and "intended state" in this context? I presume "intended state" would be the data as currently stored in Nautobot (correct me...

We do already *have* https://nautobot.readthedocs.io/en/stable/development/, but I agree it needs significant revision and restructuring. - The "introduction" document is a bit wide-ranging, and I think a lot of the project...

We'll need to think about how this intersects with potentially removing the `commit` flag altogether (#1991).

I believe your goal here is to be able to model replacing a device with new hardware in the same role? In that case I think the current supported workflow...

My immediate concern is that going in that direction would be directly counter to the goal of adding natural keys for all models, since by definition a natural key is...