nautobot 2.4.3__py3-none-any.whl → 2.4.5__py3-none-any.whl

nautobot/project-static/docs/development/apps/index.html

@@ -9190,10 +9190,6 @@
 <p>This documentation covers the development of custom Apps for Nautobot. Nautobot apps are essentially self-contained <a href="https://docs.djangoproject.com/en/stable/ref/applications/">Django applications</a> which integrate with Nautobot to provide custom functionality. Since the development of Django applications is already very well-documented, this will only be covering the aspects that are specific to Nautobot.</p>
 <p>Apps can <a href="index.html#capabilities">do a lot of different things</a>, all of which will be covered in detail in this document.
 Keep in mind that each piece of functionality is entirely optional. For example, if your app merely adds a piece of middleware or an API endpoint for existing data, there's no need to define any new models.</p>
-<details class="version-changed">
-<summary>Changed in version 1.5.2</summary>
-<p>The <code>nautobot.apps</code> namespace was added in Nautobot 1.5.2. If developing apps to be backwards-compatible with older versions of Nautobot, please refer to the app developer documentation of your required Nautobot version.</p>
-</details>
 <div class="admonition tip">
 <p class="admonition-title">Tip</p>
 <p>The app detail view (<code>/apps/installed-apps/&lt;app_name&gt;/</code>, accessible via <strong>Apps -&gt; Installed Apps</strong> in the navigation menu, then selecting a specific app) provides in-depth information about which features any installed app is implementing or making use of.</p>
@@ -9207,48 +9203,19 @@ Keep in mind that each piece of functionality is entirely optional. For example,
 <li><strong>Add navigation menu items.</strong> An App can extend the navigation menus with new links and buttons or even entirely new menus.</li>
 <li><strong>Add home page content.</strong> An App can add custom items or custom panels to the Nautobot home page.</li>
 <li><strong>Add content to existing model detail views.</strong> An App can inject custom HTML content within the view of a core Nautobot model. This content can appear in the left column, right column, or full width of the page, and can also include custom buttons at the top of the page.</li>
-</ul>
-<details class="version-added">
-<summary>Added in version 1.2.0</summary>
-<ul>
 <li><strong>Add a banner.</strong> An App can add a custom banner to the top of any appropriate views.</li>
-</ul>
-</details>
-<details class="version-added">
-<summary>Added in version 1.4.0</summary>
-<ul>
 <li><strong>Add extra tabs to existing model detail views.</strong> An App can inject additional tabs which will appear at the end of the object detail tabs list.</li>
 </ul>
-</details>
 <h3 id="extend-and-customize-existing-nautobot-functionality">Extend and customize existing Nautobot functionality<a class="headerlink" href="#extend-and-customize-existing-nautobot-functionality" title="Permanent link">&para;</a></h3>
 <ul>
 <li><strong>Add custom validation logic to existing data models.</strong> An App can provide additional logic to customize the rules for validating created/updated data records.</li>
 <li><strong>Provide Jobs.</strong> An App can serve as a convenient way to package and install <a href="../../user-guide/platform-functionality/jobs/index.html">Jobs</a>.</li>
 <li><strong>Add additional Git data types.</strong> An App can add support for processing additional types of data stored in a <a href="../../user-guide/platform-functionality/gitrepository.html">Git repository</a>.</li>
-</ul>
-<details class="version-added">
-<summary>Added in version 1.1.0</summary>
-<ul>
 <li><strong>Register additional Jinja2 filters.</strong> An App can define custom Jinja2 filters to be used in computed fields, webhooks, custom links, and export templates.</li>
-</ul>
-</details>
-<details class="version-added">
-<summary>Added in version 1.2.0</summary>
-<ul>
-<li>
-<p><strong>Populate extensibility features in the database.</strong> An App can add content to the Nautobot database when installed, such as automatically creating new custom fields, relationships, and so forth.</p>
-</li>
-<li>
-<p><strong>Add additional secrets providers.</strong> An App can add support for retrieving <a href="../../user-guide/platform-functionality/secret.html">Secret</a> values from additional sources or external systems.</p>
-</li>
-</ul>
-</details>
-<details class="version-added">
-<summary>Added in version 1.4.0</summary>
-<ul>
+<li><strong>Populate extensibility features in the database.</strong> An App can add content to the Nautobot database when installed, such as automatically creating new custom fields, relationships, and so forth.</li>
+<li><strong>Add additional secrets providers.</strong> An App can add support for retrieving <a href="../../user-guide/platform-functionality/secret.html">Secret</a> values from additional sources or external systems.</li>
 <li><strong>Override already-defined views.</strong> An App can define a view which can be set to override a view from the core set of views or another App's view.</li>
 </ul>
-</details>
 <h3 id="add-entirely-new-features">Add entirely new features<a class="headerlink" href="#add-entirely-new-features" title="Permanent link">&para;</a></h3>
 <ul>
 <li><strong>Add new data models.</strong> An App can introduce one or more models to hold data. (A model is essentially a table in the SQL database.) These models can be integrated with core implementations of GraphQL, webhooks, logging, custom relationships, custom fields, and tags.</li>

nautobot/project-static/docs/development/apps/migration/code-updates.html

@@ -9538,7 +9538,7 @@
 </tr>
 <tr>
 <td>nautobot.utilities.utils</td>
-<td>ensure_content_type_and_field_name_inquery_params</td>
+<td>ensure_content_type_and_field_name_in_query_params</td>
 <td>nautobot.core.utils.requests</td>
 </tr>
 <tr>

nautobot/project-static/docs/development/core/application-registry.html

@@ -9370,9 +9370,6 @@
 </code></pre></div>
 <p>Apps may extend this dictionary with additional data sources and/or data types by calling <code>extras.registry.register_datasource_contents()</code> as desired.</p>
 <h3 id="homepage_layout"><code>homepage_layout</code><a class="headerlink" href="#homepage_layout" title="Permanent link">&para;</a></h3>
-<details class="version-added">
-<summary>Added in version 1.2.0</summary>
-</details>
 <p>A dictionary holding information about the layout of Nautobot's homepage. Each app may register homepage panels and items using objects from the generic app class. Each object has a weight attribute allowing the developer to define the position of the object.</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a><span class="p">{</span>
 <a id="__codelineno-2-2" name="__codelineno-2-2" href="#__codelineno-2-2"></a>    <span class="s2">&quot;panels&quot;</span><span class="p">:</span> <span class="p">{</span>
@@ -9445,9 +9442,6 @@
 </code></pre></div>
 <p>For more information visit <a href="model-features.html">model-features</a>.</p>
 <h3 id="nav_menu"><code>nav_menu</code><a class="headerlink" href="#nav_menu" title="Permanent link">&para;</a></h3>
-<details class="version-added">
-<summary>Added in version 1.1.0</summary>
-</details>
 <p>Navigation menu items provided by Nautobot applications. Each app may register its navbar configuration inside of the <code>nav_menu</code> dictionary using <code>navigation.py</code>. Tabs are stored in the top level moving down to groups, items and buttons. Tabs, groups and items can be modified by using the key values inside other core applications and Apps. The <code>nav_menu</code> dict should never be modified directly.</p>
 <p>Example:</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-5-1" name="__codelineno-5-1" href="#__codelineno-5-1"></a><span class="p">{</span>

nautobot/project-static/docs/development/core/best-practices.html

@@ -8333,15 +8333,6 @@
       </ul>
     </nav>
   
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#using-nautobotuiviewset-for-app-development" class="md-nav__link">
-    <span class="md-ellipsis">
-      Using NautobotUIViewSet for App Development
-    </span>
-  </a>
-  
 </li>
       
     </ul>
@@ -9578,15 +9569,6 @@
       </ul>
     </nav>
   
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#using-nautobotuiviewset-for-app-development" class="md-nav__link">
-    <span class="md-ellipsis">
-      Using NautobotUIViewSet for App Development
-    </span>
-  </a>
-  
 </li>
       
     </ul>
@@ -9761,10 +9743,6 @@ For most purposes, this is not the case you are intending to check!</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-5-1" name="__codelineno-5-1" href="#__codelineno-5-1"></a><span class="kn">from</span> <span class="nn">nautobot.core.utils.lookup</span> <span class="kn">import</span> <span class="n">get_route_for_model</span>
 </code></pre></div>
 <p>This utility function supports both UI and API views for both Nautobot core apps and Nautobot Apps.</p>
-<details class="version-added">
-<summary>Added in version 1.4.3</summary>
-<p>Support for generating API routes was added to <code>get_route_for_model()</code> by passing the argument <code>api=True</code>.</p>
-</details>
 <h3 id="ui-routes">UI Routes<a class="headerlink" href="#ui-routes" title="Permanent link">&para;</a></h3>
 <p>Instead of:</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-6-1" name="__codelineno-6-1" href="#__codelineno-6-1"></a><span class="n">route</span> <span class="o">=</span> <span class="sa">f</span><span class="s2">&quot;</span><span class="si">{</span><span class="n">model</span><span class="o">.</span><span class="n">_meta</span><span class="o">.</span><span class="n">app_label</span><span class="si">}</span><span class="s2">:</span><span class="si">{</span><span class="n">model</span><span class="o">.</span><span class="n">_meta</span><span class="o">.</span><span class="n">model_name</span><span class="si">}</span><span class="s2">_list&quot;</span>
@@ -10054,11 +10032,6 @@ For most purposes, this is not the case you are intending to check!</p>
 <li>For exceptions such as <code>DeviceFilterSet.has_primary_ip</code> where it checks for both <code>Device.primary_ip4</code> OR <code>Device.primary_ip6</code>, method filters may still be necessary, however, they would be <strong>the exception and not the norm.</strong></li>
 <li>The good news is that in the core there are not that many of these filter methods defined, but we also don’t want to see them continue to proliferate.</li>
 </ul>
-<h2 id="using-nautobotuiviewset-for-app-development">Using NautobotUIViewSet for App Development<a class="headerlink" href="#using-nautobotuiviewset-for-app-development" title="Permanent link">&para;</a></h2>
-<details class="version-added">
-<summary>Added in version 1.4.0</summary>
-<p>Using <code>NautobotUIViewSet</code> for <a href="../apps/api/views/nautobotuiviewset.html">App development</a> is strongly recommended.</p>
-</details>
 
 
 

nautobot/project-static/docs/development/core/docker-compose-advanced-use-cases.html

@@ -8208,6 +8208,30 @@
     </span>
   </a>
   
+    <nav class="md-nav" aria-label="Remote Debugging Configuration">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#running-inside-the-nautobot-workspace" class="md-nav__link">
+    <span class="md-ellipsis">
+      Running inside the Nautobot workspace
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#adding-nautobot-folder-to-an-existing-workspace" class="md-nav__link">
+    <span class="md-ellipsis">
+      Adding Nautobot folder to an existing workspace
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
       </ul>
@@ -9450,6 +9474,30 @@
     </span>
   </a>
   
+    <nav class="md-nav" aria-label="Remote Debugging Configuration">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#running-inside-the-nautobot-workspace" class="md-nav__link">
+    <span class="md-ellipsis">
+      Running inside the Nautobot workspace
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#adding-nautobot-folder-to-an-existing-workspace" class="md-nav__link">
+    <span class="md-ellipsis">
+      Adding Nautobot folder to an existing workspace
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
       </ul>
@@ -9486,6 +9534,7 @@
 <li><code>compose_dir</code>: the full path to the directory containing the Docker Compose YAML files (default: <code>"&lt;nautobot source directory&gt;/development"</code>)</li>
 <li><code>compose_files</code>: the Docker Compose YAML file(s) to use (default: <code>["docker-compose.yml", "docker-compose.postgres.yml", "docker-compose.dev.yml"]</code>)</li>
 <li><code>docker_image_names_main</code> and <code>docker_image_names_develop</code>: Used when <a href="release-checklist.html#publish-docker-images">building Docker images for publication</a>; you shouldn't generally need to change these.</li>
+<li><code>ephemeral_ports</code>: Setting this value to <code>True</code> will make all Nautobot containers with published ports expose themselves with dynamic ports. This is useful when running multiple Nautobot versions at the same time on the same machine so you won't experience system port conflicts.</li>
 </ul>
 <p>These setting may be overridden several different ways (from highest to lowest precedence):</p>
 <ul>
@@ -9621,8 +9670,13 @@
 <li>As a last step open the folder <code>/opt/nautobot</code> in VS Code.</li>
 </ul>
 <h3 id="remote-debugging-configuration">Remote Debugging Configuration<a class="headerlink" href="#remote-debugging-configuration" title="Permanent link">&para;</a></h3>
-<p>Using the Remote-Attach functionality of VS Code debugger is an alternative to debugging in a development container. This allows a local VS Code instance to connect to a remote container and debug the code running in the container the same way as when debugging locally.</p>
-<p>Follow the steps below to configure VS Code to debug Nautobot and Celery Worker running in a remote container:</p>
+<p>Using the <a href="https://code.visualstudio.com/docs/python/debugging#_debugging-by-attaching-over-a-network-connection">Remote-Attach functionality of VS Code</a> debugger is an alternative to debugging in a development container. This allows a local VS Code instance to connect to a remote container and debug the code running in the container the same way as when debugging locally. To learn more about debugging in VSCode, please <a href="https://code.visualstudio.com/docs/editor/debugging">follow the official docs</a>.</p>
+<p>Follow either of the options below to configure VS Code to debug Nautobot and Celery Worker running in a remote container:</p>
+<h4 id="running-inside-the-nautobot-workspace">Running inside the Nautobot workspace<a class="headerlink" href="#running-inside-the-nautobot-workspace" title="Permanent link">&para;</a></h4>
+<p>If you have opened the project via the workspace file <code>nautobot.code-workspace</code> then there are two debug configurations for remote debugging available. These can be run via one of the debug tasks:
+- <code>Python: Nautobot (Remote)</code> or
+- <code>Python: Nautobot-Celery (Remote)</code></p>
+<h4 id="adding-nautobot-folder-to-an-existing-workspace">Adding Nautobot folder to an existing workspace<a class="headerlink" href="#adding-nautobot-folder-to-an-existing-workspace" title="Permanent link">&para;</a></h4>
 <ol>
 <li>
 <p><strong>Configure <code>invoke.yml</code> to use the <code>docker-compose.vscode-rdb.yml</code> file.</strong></p>
@@ -9662,10 +9716,10 @@ then copy the <code>launch:</code> values to the <code>.vscode/launch.json</code
 <a id="__codelineno-9-12" name="__codelineno-9-12" href="#__codelineno-9-12"></a><span class="w">  </span><span class="p">]</span>
 <a id="__codelineno-9-13" name="__codelineno-9-13" href="#__codelineno-9-13"></a><span class="p">}</span>
 </code></pre></div>
-</li>
-</ol>
 <p>It is now possible to debug the containerized Nautobot and Celery Worker using the VS Code debugger.</p>
 <p>After restarting the Celery-Worker container you need to restart the debug session.</p>
+</li>
+</ol>
 
 
 

nautobot/project-static/docs/development/core/getting-started.html

@@ -10359,10 +10359,6 @@
 <p>You may install Poetry in your user environment by running:</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-15-1" name="__codelineno-15-1" href="#__codelineno-15-1"></a>curl -sSL https://install.python-poetry.org | python3 -
 </code></pre></div>
-<details class="version-changed">
-<summary>Changed in version 1.5.6</summary>
-<p>Poetry 1.3+ is required to be able to install packages against the latest lockfile.</p>
-</details>
 <div class="admonition danger">
 <p class="admonition-title">Danger</p>
 <p>Always utilize this documented method to install Poetry for use when developing Nautobot.</p>
@@ -10549,7 +10545,7 @@
 <p>Do not use <code>poetry run nautobot-server runserver</code> as it will crash unless you also pass the <code>--noreload</code> flag, which somewhat defeats the purpose of using the development server. It is recommended to use <code>nautobot-server runserver</code> from within an active virtualenv (e.g. <code>poetry shell</code>). This is a <a href="https://github.com/python-poetry/poetry/issues/2435">known issue with Django and Poetry</a>.</p>
 </div>
 <p>Please see the <a href="https://docs.djangoproject.com/en/stable/ref/django-admin/#runserver">official Django documentation on <code>runserver</code></a> for more information.</p>
-<p>You can connect to the development server at <code>localhost:8080</code>.</p>
+<p>You can connect to the development server in your local web browser at <code>http://localhost:8080</code>. If you are using the ephemeral ports feature (disabled by default), you can make use of the command, <code>invoke open-nautobot-web</code>. This will open up the default web-browser on your system pointing to the correct Nautobot admin port. Note that this command can be used regardless of ephemeral port mode.</p>
 <h3 id="starting-the-worker-server">Starting the Worker Server<a class="headerlink" href="#starting-the-worker-server" title="Permanent link">&para;</a></h3>
 <p>In order to run Nautobot Jobs or anything that requires a worker you must start a Celery worker.</p>
 <p>The worker is started in Docker Workflow with <a href="https://pythonhosted.org/watchdog/">watchdog</a> and can be setup to be started with watchdog in the Virtual Environment Workflow. Watchdog provides a similar experience to the Django lightweight HTTP/WSGI for restarting your application automatically. Watchdog can watch for changes on your filesystem, this is helpful when adjusting existing Python files to not have to restart the Celery worker when testing jobs.</p>
@@ -10752,10 +10748,10 @@
 <p class="admonition-title">Tip</p>
 <p>You may also use <code>invoke integration-test</code> in the Virtual Environment workflow given that the <code>selenium</code> container is running, and that the <code>INVOKE_NAUTOBOT_LOCAL=True</code> environment variable has been set.</p>
 </div>
-<details class="version-changed">
-<summary>Changed in version 1.5.11</summary>
+<div class="admonition tip">
+<p class="admonition-title">Tip</p>
 <p>The <code>--cache-test-fixtures</code> argument was added to the <code>invoke integration-test</code> and <code>nautobot-server test</code> commands to allow for caching of test factory data between test runs. See the <a href="testing.html#factory-caching">factories documentation</a> for more information.</p>
-</details>
+</div>
 <h5 id="customizing-integration-test-executions">Customizing Integration Test Executions<a class="headerlink" href="#customizing-integration-test-executions" title="Permanent link">&para;</a></h5>
 <p>The following environment variables can be provided when running tests to customize where Nautobot looks for Selenium and where Selenium looks for Nautobot. If using the default setup documented above, there is no need to customize these.</p>
 <ul>
@@ -10845,27 +10841,27 @@
 <p>Some features require documentation updates or new documentation to be written. The documentation files can be found in the <code>docs</code> directory. To preview these changes locally, you can use <code>mkdocs</code>.</p>
 <p>For substantial changes to the code (including new features, removal of existing features, or significant changes in behavior) you should always make corresponding documentation updates. Nautobot's documentation pipeline includes a custom plugin for <code>mkdocs</code> that adds a few useful macros for annotating such changes:</p>
 <ul>
-<li><code>+++ 1.4.3</code>, on a line by itself, is a shorthand for <code>!!! version-added "Added in version 1.4.3"</code></li>
-<li><code>+/- 1.4.3</code>, on a line by itself, is a shorthand for <code>!!! version-changed "Changed in version 1.4.3"</code></li>
-<li><code>--- 1.4.3</code>, on a line by itself, is a shorthand for <code>!!! version-removed "Removed in version 1.4.3"</code></li>
+<li><code>+++ 2.4.3</code>, on a line by itself, is a shorthand for <code>!!! version-added "Added in version 2.4.3"</code></li>
+<li><code>+/- 2.4.3</code>, on a line by itself, is a shorthand for <code>!!! version-changed "Changed in version 2.4.3"</code></li>
+<li><code>--- 2.4.3</code>, on a line by itself, is a shorthand for <code>!!! version-removed "Removed in version 2.4.3"</code></li>
 </ul>
 <p>These admonitions in turn appear in the rendered documentation as follows:</p>
 <details class="version-added">
-<summary>Added in version 1.4.3</summary>
+<summary>Added in version 2.4.3</summary>
 </details>
 <details class="version-changed">
-<summary>Changed in version 1.4.3</summary>
+<summary>Changed in version 2.4.3</summary>
 </details>
 <details class="version-removed">
-<summary>Removed in version 1.4.3</summary>
+<summary>Removed in version 2.4.3</summary>
 </details>
 <p>You can also add text to any of these admonitions for further clarity, for example:</p>
-<div class="highlight"><pre><span></span><code>??? version-added &quot;Added in version 1.4.3&quot;
+<div class="highlight"><pre><span></span><code>??? version-added &quot;Added in version 2.4.3&quot;
     The custom `mkdocs` plugin was added.
 </code></pre></div>
 <p>will render as:</p>
 <details class="version-added">
-<summary>Added in version 1.4.3</summary>
+<summary>Added in version 2.4.3</summary>
 <p>The custom <code>mkdocs</code> plugin was added.</p>
 </details>
 <div class="admonition caution">

nautobot/project-static/docs/development/core/homepage.html

@@ -9176,9 +9176,6 @@
 
 
 <h1 id="populating-the-home-page">Populating the Home Page<a class="headerlink" href="#populating-the-home-page" title="Permanent link">&para;</a></h1>
-<details class="version-added">
-<summary>Added in version 1.2.0</summary>
-</details>
 <p>Both core applications and Apps can contribute items to the Nautobot home page by defining <code>layout</code> inside of their app's <code>homepage.py</code>. Using a key and weight system, a developer can integrate amongst existing home page panels or can create entirely new panels as desired.</p>
 <h2 id="adding-a-new-home-page-panel">Adding a new Home Page Panel<a class="headerlink" href="#adding-a-new-home-page-panel" title="Permanent link">&para;</a></h2>
 <p>Each panel on the home page is defined by a <code>HomePagePanel</code> object. A <code>HomePagePanel</code> may contain either or both of <code>HomePageItem</code> and/or <code>HomePageGroup</code> objects, or may define custom content via a referenced Django template. A <code>HomePageGroup</code> may itself contain <code>HomePageItem</code> objects as well, and individual <code>HomePageItem</code> objects may also reference custom Django templates.</p>

nautobot/project-static/docs/development/core/style-guide.html

@@ -9471,10 +9471,6 @@
 <li>
 <p>The combination of <code>nautobot.core.forms.BootstrapMixin</code>, <code>nautobot.extras.forms.CustomFieldModelFormMixin</code>, <code>nautobot.extras.forms.RelationshipModelFormMixin</code> and <code>nautobot.extras.forms.NoteModelFormMixin</code> is such a common use case throughout the code base that they have a helper class which combines all of these at <code>nautobot.extras.forms.NautobotModelForm</code>. Use this helper class if you need the functionality from these classes.</p>
 </li>
-</ul>
-<details class="version-added">
-<summary>Added in version 1.4.0</summary>
-<ul>
 <li>
 <p>Similarly, for filter forms, <code>nautobot.extras.forms.NautobotFilterForm</code> combines <code>nautobot.core.forms.BootstrapMixin</code>, <code>nautobot.extras.forms.ContactTeamModelFilterFormMixin</code> (since Nautobot 2.3.0), <code>nautobot.extras.forms.CustomFieldModelFilterFormMixin</code>, and <code>nautobot.extras.forms.RelationshipModelFilterFormMixin</code>, and should be used where appropriate.</p>
 </li>
@@ -9491,7 +9487,6 @@
 <p>API Views for most models should inherit from <code>nautobot.extras.api.views.NautobotModelViewSet</code>. Only use more abstract base classes such as <code>ModelViewSet</code> where absolutely required.</p>
 </li>
 </ul>
-</details>
 <h2 id="branding">Branding<a class="headerlink" href="#branding" title="Permanent link">&para;</a></h2>
 <ul>
 <li>When referring to Nautobot in writing, use the proper form "<code>Nautobot</code>," with the letter N. The lowercase form "<code>nautobot</code>" should be used in code, filenames, etc.</li>

nautobot/project-static/docs/development/core/templates.html

@@ -9308,9 +9308,6 @@ This document presents these templates and their features.</p>
 <p>You can use these templates as the basis for your templates by calling <code>{% extends '&lt;template_name&gt;' %}</code>
 at the top of your template file.</p>
 <h2 id="object-detail">Object Detail<a class="headerlink" href="#object-detail" title="Permanent link">&para;</a></h2>
-<details class="version-added">
-<summary>Added in version 1.2.0</summary>
-</details>
 <p>The most customizable template is <code>generic/object_retrieve.html</code>, as object detail views have a wide range of specific requirements to be accommodated. It provides the following blocks:</p>
 <ul>
 <li><code>header</code>: overloading this block allows for changing the entire top row of

nautobot/project-static/docs/development/core/testing.html

@@ -9549,9 +9549,6 @@
 <h3 id="troubleshooting-integration-tests">Troubleshooting Integration Tests<a class="headerlink" href="#troubleshooting-integration-tests" title="Permanent link">&para;</a></h3>
 <p>Because integration tests normally involve interacting with Nautobot through a browser via <a href="https://www.selenium.dev/selenium/docs/api/py/index.html">Selenium</a> and the <a href="https://splinter.readthedocs.io/en/latest/">Splinter</a> wrapper library, they can be difficult to troubleshoot directly from the Python code when a failure occurs. A common troubleshooting technique is to add a <code>breakpoint()</code> at the appropriate place in the Python test code (i.e., immediately prior to the observed failure). When the breakpoint is hit and the test pauses, you can then use a VNC viewer application (such as macOS's "Screen Sharing" app) to connect to the running Selenium instance (<code>localhost:15900</code> if using the Docker development environment; the default password if prompted is simply "<code>secret</code>"). This will allow you to interact live with the testing web browser in its current state and can often provide invaluable insight into the nature of any test failure.</p>
 <h2 id="factories">Factories<a class="headerlink" href="#factories" title="Permanent link">&para;</a></h2>
-<details class="version-added">
-<summary>Added in version 1.5.0</summary>
-</details>
 <p>Nautobot uses the <a href="https://factoryboy.readthedocs.io/en/stable/"><code>factory_boy</code></a> library as a way to generate randomized but plausible database data for use in unit and integration tests, or for convenience in populating a local development instance.</p>
 <p>Factories for each Nautobot app's models are defined in the corresponding <code>nautobot/APPNAME/factory.py</code> files. Helper classes and functions for certain common patterns are defined in <code>nautobot/core/factory.py</code>. Factories can be used directly from <code>nautobot-server nbshell</code> so long as you have <code>factory_boy</code> installed. Examples:</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-1-1" name="__codelineno-1-1" href="#__codelineno-1-1"></a><span class="o">&gt;&gt;&gt;</span> <span class="kn">from</span> <span class="nn">nautobot.tenancy.factory</span> <span class="kn">import</span> <span class="n">TenantFactory</span><span class="p">,</span> <span class="n">TenantGroupFactory</span>
@@ -9580,9 +9577,6 @@
 <p>In short, we should only have one place in our tests where factories are called, and that's the <code>generate_test_data</code> management command. Individual tests should use standard <code>create()</code> or <code>save()</code> model methods, never factories.</p>
 </div>
 <h3 id="factory-caching">Factory Caching<a class="headerlink" href="#factory-caching" title="Permanent link">&para;</a></h3>
-<details class="version-added">
-<summary>Added in version 1.5.11</summary>
-</details>
 <p>To reduce the time taken between multiple test runs, a new argument has been added to the <code>nautobot-server test</code> command: <code>--cache-test-fixtures</code>. When running tests with <code>--cache-test-fixtures</code> for the first time, after the factory data has been generated it will be saved to a <code>factory_dump.json</code> file in the <code>development</code> directory. On subsequent runs of unit or integration tests, if <code>--cache-test-fixtures</code> is again specified (hint: it is included by default when running <code>invoke unittest</code> or <code>invoke integration-test</code>), the factory data will be loaded from the file instead of being generated again. This can significantly reduce the time taken to run tests.</p>
 <details class="version-changed">
 <summary>Changed in version 2.2.7 — Hashing of migrations in the factory dump</summary>
@@ -9601,9 +9595,6 @@
 </ol>
 </div>
 <h2 id="performance-tests">Performance Tests<a class="headerlink" href="#performance-tests" title="Permanent link">&para;</a></h2>
-<details class="version-added">
-<summary>Added in version 1.5.0</summary>
-</details>
 <h3 id="running-performance-tests">Running Performance Tests<a class="headerlink" href="#running-performance-tests" title="Permanent link">&para;</a></h3>
 <p>Nautobot uses <a href="https://pypi.org/project/django-slowtests/"><code>django-slowtests</code></a> to run performance tests. To run performance tests, you need to install the <code>django-slowtests</code> package.
 Once you install the package, you can do <code>invoke performance-test</code> or <code>invoke unittest --performance-test</code> to run unit tests with <code>NautobotPerformanceTestRunner</code>. The invoke commands will automatically add <code>--testrunner nautobot.core.tests.runner.NautobotPerformanceTestRunner</code> to the <code>coverage run</code> command and this flag will replace the default <code>NautobotTestRunner</code> while retaining all its functionalities with the addition of performance evaluation after test runs.</p>