nautobot 2.0.0a2__py3-none-any.whl → 2.0.0b1__py3-none-any.whl

nautobot/docs/administration/nautobot-server.md

@@ -286,21 +286,6 @@ Configuration file created at '/home/example/.nautobot/nautobot_config.py
 
 For more information on configuring Nautobot for the first time or on more advanced configuration patterns, please see the guide on [Nautobot Configuration](../configuration/index.md).
 
-### `invalidate`
-
-`nautobot-server invalidate`
-
-Invalidates cache for entire app, model or particular instance. Most commonly you will see us recommend clearing the entire cache using `invalidate all`:
-
-```no-highlight
-nautobot-server invalidate all
-```
-
-There are a number of other options not covered here.
-
-!!! note
-    This is a built-in management command provided by the [Cacheops plugin](https://github.com/Suor/django-cacheops) Nautobot for caching. Please see the official [Cacheops documentation on `invalidate`](https://github.com/Suor/django-cacheops#invalidation) for more information.
-
 ### `loaddata`
 
 `nautobot-server loaddata --traceback nautobot_dump.json`
@@ -395,10 +380,10 @@ from django.db.models import Avg, Case, Count, F, Max, Min, Prefetch, Q, Sum, Wh
 from django.utils import timezone
 from django.urls import reverse
 from django.db.models import Exists, OuterRef, Subquery
-# Django version 3.2.16
-# Nautobot version 2.0.0a0
+# Django version 3.2.18
+# Nautobot version 2.0.0a2
 # Example Nautobot App version 1.0.0
-Python 3.7.13 (default, May 11 2022, 08:57:12)
+Python 3.8.16 (default, Mar 23 2023, 04:48:11)
 [GCC 10.2.1 20210110] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
@@ -420,20 +405,19 @@ This will run the following management commands with default settings, in order:
 - `collectstatic`
 - `remove_stale_contenttypes`
 - `clearsessions`
-- `invalidate all`
 
 !!! note
     Commands listed here that are not covered in this document here are Django built-in commands.
 
+--- 2.0.0
+    With the removal of `django-cacheops` from Nautobot, this command no longer runs `invalidate all`.
+
 `--no-clearsessions`  
 Do not automatically clean out expired sessions.
 
 `--no-collectstatic`  
 Do not automatically collect static files into a single location.
 
-`--no-invalidate-all`  
-Do not automatically invalidate cache for entire application.
-
 `--no-migrate`  
 Do not automatically perform any database migrations.
 
@@ -443,6 +427,9 @@ Do not automatically remove stale content types.
 `--no-trace-paths`  
 Do not automatically generate missing cable paths.
 
+--- 2.0.0
+    With the removal of `django-cacheops` from Nautobot, the `--no-invalidate-all` flag was removed from this command.
+
 ```no-highlight
 nautobot-server post_upgrade
 ```
@@ -473,8 +460,6 @@ Collecting static files...
 Removing stale content types...
 
 Removing expired sessions...
-
-Invalidating cache...
 ```
 
 ### `remove_stale_scheduled_jobs`

nautobot/docs/administration/nautobot-shell.md

@@ -58,10 +58,10 @@ from django.db.models import Avg, Case, Count, F, Max, Min, Prefetch, Q, Sum, Wh
 from django.utils import timezone
 from django.urls import reverse
 from django.db.models import Exists, OuterRef, Subquery
-# Django version 3.2.16
-# Nautobot version 2.0.0a0
+# Django version 3.2.18
+# Nautobot version 2.0.0a2
 # Example Nautobot App version 1.0.0
-Python 3.7.13 (default, May 11 2022, 08:57:12)
+Python 3.8.16 (default, Mar 23 2023, 04:48:11)
 [GCC 10.2.1 20210110] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
@@ -116,7 +116,7 @@ To retrieve a particular object (typically by its primary key or other unique fi
 In most cases, you will want to retrieve only a specific subset of objects. To filter a queryset, replace `all()` with `filter()` and pass one or more keyword arguments. For example:
 
 ```python
->>> Device.objects.filter(status__slug="active")
+>>> Device.objects.filter(status__name="Active")
 <QuerySet [<Device: TestDevice1>, <Device: TestDevice2>, <Device: TestDevice3>,
 <Device: TestDevice8>, <Device: TestDevice9>, '...(remaining elements truncated)...']>
 ```
@@ -124,14 +124,14 @@ In most cases, you will want to retrieve only a specific subset of objects. To f
 Querysets support slicing to return a specific range of objects.
 
 ```python
->>> Device.objects.filter(status__slug="active")[:3]
+>>> Device.objects.filter(status__name="Active")[:3]
 <QuerySet [<Device: TestDevice1>, <Device: TestDevice2>, <Device: TestDevice3>]>
 ```
 
 The `count()` method can be appended to the queryset to return a count of objects rather than the full list.
 
 ```python
->>> Device.objects.filter(status__slug="active").count()
+>>> Device.objects.filter(status__name="Active").count()
 982
 ```
 

nautobot/docs/administration/replicating-nautobot.md

@@ -68,13 +68,3 @@ To extract the saved archive into a new installation, run the following from the
 ```no-highlight
 tar -xf nautobot_media.tar.gz
 ```
-
----
-
-## Cache Invalidation
-
-If you are migrating your instance of Nautobot to a different machine, be sure to first invalidate the cache on the original instance by issuing the `invalidate all` management command (within the Python virtual environment):
-
-```no-highlight
-nautobot-server invalidate all
-```

nautobot/docs/configuration/index.md

@@ -123,10 +123,10 @@ Output:
 ..
 from django.conf import settings
 ...
-# Django version 3.2.16
-# Nautobot version 2.0.0a0
+# Django version 3.2.18
+# Nautobot version 2.0.0a2
 ...
-Python 3.7.13 (default, May 11 2022, 08:57:12)
+Python 3.8.16 (default, Mar 23 2023, 04:48:11)
 [GCC 10.2.1 20210110] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
@@ -161,17 +161,17 @@ If you attempt to modify `INSTALLED_APPS` yourself, you might see an error such
 Traceback (most recent call last):
   File "/usr/local/bin/nautobot-server", line 8, in <module>
     sys.exit(main())
-  File "/usr/local/lib/python3.7/site-packages/nautobot/core/cli.py", line 53, in main
+  File "/usr/local/lib/python3.8/site-packages/nautobot/core/cli.py", line 53, in main
     initializer=_configure_settings,  # Called after defaults
-  File "/usr/local/lib/python3.7/site-packages/nautobot/core/runner/runner.py", line 193, in run_app
+  File "/usr/local/lib/python3.8/site-packages/nautobot/core/runner/runner.py", line 193, in run_app
     management.execute_from_command_line([runner_name, command] + command_args)
-  File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
+  File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
     utility.execute()
-  File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 377, in execute
+  File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 377, in execute
     django.setup()
-  File "/usr/local/lib/python3.7/site-packages/django/__init__.py", line 24, in setup
+  File "/usr/local/lib/python3.8/site-packages/django/__init__.py", line 24, in setup
     apps.populate(settings.INSTALLED_APPS)
-  File "/usr/local/lib/python3.7/site-packages/django/apps/registry.py", line 95, in populate
+  File "/usr/local/lib/python3.8/site-packages/django/apps/registry.py", line 95, in populate
     "duplicates: %s" % app_config.label)
 django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: health_check
 ```

nautobot/docs/configuration/optional-settings.md

@@ -153,42 +153,6 @@ If a custom URL is not provided for any of the links, the default link within th
 
 ---
 
-## CACHEOPS_DEFAULTS
-
-Default: `{'timeout': 900}` (15 minutes, in seconds)
-
-Environment Variable: `NAUTOBOT_CACHEOPS_TIMEOUT` (timeout value only)
-
-!!! warning
-    It is an error to set the timeout value to `0`. If you wish to disable caching, please use [`CACHEOPS_ENABLED`](#cacheops_enabled).
-
-Various defaults for caching, the most important of which being the cache timeout. The `timeout` is the number of seconds that cache entries will be retained before expiring.
-
----
-
-## CACHEOPS_ENABLED
-
-Default: `False`
-
-Environment Variable: `NAUTOBOT_CACHEOPS_ENABLED`
-
-A boolean that turns on/off caching.
-
-!!! check "Changed in 1.5.0"
-    Cachopes is disabled by default and will be removed entirely in a future release.
-
-If set to `False`, all caching is bypassed and Nautobot operates as if there is no cache.
-
----
-
-## CACHEOPS_HEALTH_CHECK_ENABLED
-
-Default: `False`
-
-A boolean that turns on/off health checks for the Redis server connection utilized by Cacheops. Most deployments share a Redis server with `django-redis` as such we only need to check the health of Redis one time.  If you are using a separate Redis deployment for Cacheops, please consider enabling this to monitor that Redis deployment.  Keep in mind the more health checks enabled the longer the health checks will take and timeouts might need to be increased.
-
----
-
 ## CELERY_BROKER_TRANSPORT_OPTIONS
 
 Default: `{}`
@@ -257,6 +221,30 @@ case. Set this to an empty list to disable it.
 
 ---
 
+## CELERY_WORKER_REDIRECT_STDOUTS
+
++++ 2.0.0
+
+Environment Variable: `NAUTOBOT_CELERY_WORKER_REDIRECT_STDOUTS`
+
+Default: `True`
+
+If enabled stdout and stderr of running jobs will be redirected to the task logger.
+
+---
+
+## CELERY_WORKER_REDIRECT_STDOUTS_LEVEL
+
++++ 2.0.0
+
+Environment Variable: `NAUTOBOT_CELERY_WORKER_REDIRECT_STDOUTS_LEVEL`
+
+Default: `WARNING`
+
+The log level of log messages generated by redirected job stdout and stderr. Can be one of `DEBUG`, `INFO`, `WARNING`, `ERROR`, or `CRITICAL`.
+
+---
+
 ## CHANGELOG_RETENTION
 
 Default: `90`
@@ -341,26 +329,6 @@ Previously this setting was called `CORS_ORIGIN_REGEX_WHITELIST`, which still wo
 
 ---
 
-## DISABLE_PREFIX_LIST_HIERARCHY
-
-Default: `False`
-
-This setting disables rendering of the IP prefix hierarchy (parent/child relationships) in the IPAM prefix list view. With large sets of prefixes, users may encounter a performance penalty when trying to load the prefix list view due to the nature of calculating the parent/child relationships. This setting allows users to disable the hierarchy and instead only render a flat list of all prefixes in the table.
-
-A later release of Nautobot will address the underlying performance issues, and likely remove this configuration option.
-
----
-
-## ENFORCE_GLOBAL_UNIQUE
-
-Default: `False`
-
-Environment Variable: `NAUTOBOT_ENFORCE_GLOBAL_UNIQUE`
-
-By default, Nautobot will permit users to create duplicate prefixes and IP addresses in the global table (that is, those which are not assigned to any VRF). This behavior can be disabled by setting `ENFORCE_GLOBAL_UNIQUE` to `True`.
-
----
-
 ## EXEMPT_VIEW_PERMISSIONS
 
 Default: `[]` (Empty list)
@@ -764,7 +732,7 @@ Default:
 ```python
 [
     (re.compile(r"(https?://)?\S+\s*@", re.IGNORECASE), r"\1{replacement}@"),
-    (re.compile(r"(username|password|passwd|pwd)(\s*i?s?\s*:?\s*)?\S+", re.IGNORECASE), r"\1\2{replacement}"),
+    (re.compile(r"(username|password|passwd|pwd)((?:\s+is.?|:)?\s+)\S+", re.IGNORECASE), r"\1\2{replacement}"),
 ]
 ```
 
@@ -1079,6 +1047,9 @@ Default:
 +/- 1.4.10
     While running unit or integration tests via `nautobot-server test ...`, LOGGING will be set to `{}` instead of the above defaults, as verbose logging to the console is typically not desirable while running tests.
 
++/- 2.0.0
+    Unit/integration test logging was modified to send all nautobot logs to a `NullHandler` to prevent logs falling through to the last resort logger and being output to stderr.
+
 This translates to:
 
 * all messages from Django and from Nautobot of INFO severity or higher will be logged to the console.
@@ -1106,10 +1077,10 @@ Additional examples are available in the [`/examples/logging`](https://github.co
 * `django.*` - Generic Django operations (HTTP requests/responses, etc.)
 * `nautobot.<app>.<module>` - Generic form for model- or module-specific log messages
 * `nautobot.auth.*` - Authentication events
-* `nautobot.jobs.*` - Job execution (`* = JobClassName`)
-* `nautobot.graphql.*` - [GraphQL](../additional-features/graphql.md) initialization and operation.
-* `nautobot.plugins.*` - Plugin loading and activity
-* `nautobot.views.*` - Views which handle business logic for the web UI
+* `nautobot.extras.jobs.*` - Job execution (`* = JobClassName`)
+* `nautobot.core.graphql.*` - [GraphQL](../additional-features/graphql.md) initialization and operation.
+* `nautobot.extras.plugins.*` - Plugin loading and activity
+* `nautobot.core.views.generic.*` - Generic views which handle business logic for the web UI
 
 ---
 

nautobot/docs/configuration/required-settings.md

@@ -41,7 +41,7 @@ Nautobot requires access to a supported database service to store data. This ser
 * `HOST` - Name or IP address of the database server (use `localhost` if running locally)
 * `PORT` - The port to use when connecting to the database. An empty string means the default port for your selected backend. (PostgreSQL: `5432`, MySQL: `3306`)
 * `CONN_MAX_AGE` - Lifetime of a [persistent database connection](https://docs.djangoproject.com/en/stable/ref/databases/#persistent-connections), in seconds (300 is the default)
-* `ENGINE` - The database backend to use. This can be either `django.db.backends.postgresql` or `django.db.backends.mysql`.
+* `ENGINE` - The database backend to use. This can be either `django.db.backends.postgresql` or `django.db.backends.mysql`.  If `METRICS_ENABLED` is `True` this can also be either `django_prometheus.db.backends.postgresql` or `django_prometheus.db.backends.mysql`
 
 The following environment variables may also be set for each of the above values:
 
@@ -124,64 +124,16 @@ to different Redis instances/databases per feature.
 
 ### Caching
 
-Nautobot supports database query caching using [`django-cacheops`](https://github.com/Suor/django-cacheops).
-
-Caching is configured by defining the [`CACHEOPS_REDIS`](#cacheops_redis) setting which in its simplest form is just a URL.
-
 For more details on Nautobot's caching, including TLS and HA configuration, see the guide on [Caching](../additional-features/caching.md).
 
-!!! important
-    Nautobot does not utilize the built-in [Django cache framework](https://docs.djangoproject.com/en/stable/topics/cache/) to perform caching, as `django-cacheops` takes its place.
-
-#### CACHEOPS_REDIS
-
-Default: `"redis://localhost:6379/1"`
-
-Environment Variable: `NAUTOBOT_CACHEOPS_REDIS`
-
-If you wish to use SSL, you may set the URL scheme to `rediss://`, for example:
-
-```python
-CACHEOPS_REDIS = "rediss://localhost:6379/1"
-```
-
-This setting may also be a dictionary style to provide additional options such as custom TLS/SSL settings, for example:
-
-```python
-import ssl
-
-CACHEOPS_REDIS = {
-    "host": os.getenv("NAUTOBOT_REDIS_HOST", "localhost"),
-    "port": int(os.getenv("NAUTOBOT_REDIS_PORT", 6379)),
-    "password": os.getenv("NAUTOBOT_REDIS_PASSWORD", ""),
-    "ssl": True,
-    "ssl_cert_reqs": ssl.CERT_REQUIRED,
-    "ssl_ca_certs": "/opt/nautobot/redis/ca.crt",
-    "ssl_certfile": "/opt/nautobot/redis/tls.crt",
-    "ssl_keyfile": "/opt/nautobot/redis/tls.key",
-}
-```
-
-Additional settings may be available and are not covered here. Please see the official guide on [Cacheops setup](https://github.com/Suor/django-cacheops#setup).
-
-#### CACHEOPS_SENTINEL
-
-Default: `undefined`
-
-If you are using [Redis Sentinel](https://redis.io/topics/sentinel) for high-availability purposes, you must replace the [`CACHEOPS_REDIS`](#cacheops_redis) setting with [`CACHEOPS_SENTINEL`](#cacheops_sentinel). For more details on configuring Nautobot to use Redis Sentinel see [Using Redis Sentinel](../additional-features/caching.md#using-redis-sentinel). For more details on how to configure Cacheops specifically to use Redis Sentinel see the official guide on [Cacheops
-setup](https://github.com/Suor/django-cacheops#setup).
-
-!!! warning
-    [`CACHEOPS_REDIS`](#cacheops_redis) and [`CACHEOPS_SENTINEL`](#cacheops_sentinel) are mutually exclusive and will result in an error if both are set.
-
 ### Task Queuing
 
 #### CACHES
 
-The [`django-redis`](https://github.com/jazzband/django-redis) Django plugin is used to enable Redis as a concurrent write lock for preventing race conditions when allocating IP address objects. The `CACHES` setting is required to to simplify the configuration for defining queues. *It is not used for caching at this time.*
+The [`django-redis`](https://github.com/jazzband/django-redis) Django plugin is used to enable Redis as a concurrent write lock for preventing race conditions when allocating IP address objects. The `CACHES` setting is required to simplify the configuration for `django-redis`.
 
 !!! important
-    Nautobot does not utilize the built-in [Django cache framework](https://docs.djangoproject.com/en/stable/topics/cache/) (which also relies on the `CACHES` setting) to perform caching because Cacheops is being used instead as detailed just above. *Yes, we know this is confusing, which is why this is being called out explicitly!*
+    Nautobot also utilizes the built-in [Django cache framework](https://docs.djangoproject.com/en/stable/topics/cache/) (which also relies on the `CACHES` setting) to perform caching.
 
 Default:
 
@@ -192,7 +144,7 @@ Default:
 CACHES = {
     "default": {
         "BACKEND": "django_redis.cache.RedisCache",
-        "LOCATION": "redis://localhost:6379/0",
+        "LOCATION": "redis://localhost:6379/1",
         "TIMEOUT": 300,
         "OPTIONS": {
             "CLIENT_CLASS": "django_redis.client.DefaultClient",
@@ -208,6 +160,13 @@ CACHES = {
 }
 ```
 
+The following environment variables may also be set for some of the above values:
+
+* `NAUTOBOT_CACHES_BACKEND`
+
++/- 2.0.0
+    The default value of `CACHES["default"]["LOCATION"]` has changed from `redis://localhost:6379/0` to `redis://localhost:6379/1`, as Django's native caching is now taking the role previously occupied by `django-cacheops`.
+
 ### Task Queuing with Celery
 
 +++ 1.1.0

nautobot/docs/development/application-registry.md

@@ -197,19 +197,8 @@ List of GraphQL Type objects that will be added to the GraphQL schema. GraphQL o
 ]
 ```
 
-### `plugin_jobs`
-
-[Jobs](../additional-features/jobs.md) provided by plugins. A list of `Job` classes, for example:
-
-```python
-[
-    demo_data_plugin.jobs.CreateDemoData,
-    demo_data_plugin.jobs.DestroyDemoData,
-    branch_creation_plugin.jobs.CreateNewSmallBranch,
-    branch_creation_plugin.jobs.CreateNewMediumBranch,
-    branch_creation_plugin.jobs.CreateNewLargeBranch,
-]
-```
+--- 2.0.0
+    The `plugin_jobs` registry has been replaced by [`nautobot.core.celery.register_jobs`](../additional-features/jobs.md#writing-jobs) which should be called at import time by any plugin that provides jobs.
 
 ### `plugin_template_extensions`
 

nautobot/docs/development/best-practices.md

@@ -268,7 +268,8 @@ from nautobot.core.filters import NaturalKeyOrPKMultipleChoiceFilter
 
     provider = NaturalKeyOrPKMultipleChoiceFilter(
         queryset=Provider.objects.all(),
-        label="Provider (slug or ID)",
+        to_field_name="name",
+        label="Provider (name or ID)",
     )
 ```
 

nautobot/docs/development/docker-compose-advanced-use-cases.md

@@ -7,7 +7,7 @@ This section describes some of the more advanced use cases for the [Docker Compo
 The Invoke tasks have some default [configuration](http://docs.pyinvoke.org/en/stable/concepts/configuration.html) which you may want to override. Configuration properties include:
 
 - `project_name`: The name that all Docker containers will be grouped together under (default: `nautobot`, resulting in containers named `nautobot_nautobot_1`, `nautobot_redis_1`, etc.)
-- `python_ver`: the Python version which is used to build the Docker container (default: `3.7`)
+- `python_ver`: the Python version which is used to build the Docker container (default: `3.8`)
 - `local`: run the commands in the local environment vs the Docker container (default: `False`)
 - `compose_dir`: the full path to the directory containing the Docker Compose YAML files (default: `"<nautobot source directory>/development"`)
 - `compose_files`: the Docker Compose YAML file(s) to use (default: `["docker-compose.yml", "docker-compose.postgres.yml", "docker-compose.dev.yml"]`)

nautobot/docs/development/extending-models.md

@@ -2,7 +2,7 @@
 
 Below is a list of tasks to consider when adding a new field to a core model.
 
-## 1. Generate and run database migrations
+## Generate and run database migrations
 
 Django migrations are used to express changes to the database schema. In most cases, Django can generate these automatically, however very complex changes may require manual intervention. Always remember to specify a short but descriptive name when generating a new migration.
 
@@ -19,7 +19,7 @@ Where possible, try to merge related changes into a single migration. For exampl
 !!! note
     Migrations can only be merged within a release. Once a new release has been published, its migrations cannot be altered (other than for the purpose of correcting a bug).
 
-## 2. Add validation logic to `clean()`
+## Add validation logic to `clean()`
 
 If the new field introduces additional validation requirements (beyond what's included with the field itself), implement them in the model's `clean()` method. Remember to call the model's original method using `super()` before or after your custom validation as appropriate:
 
@@ -35,48 +35,46 @@ class Foo(models.Model):
             raise ValidationError()
 ```
 
-## 3. Add CSV helpers
-
-Add the name of the new field to `csv_headers` and included a CSV-friendly representation of its data in the model's `to_csv()` method. These will be used when exporting objects in CSV format.
-
-## 4. Update relevant querysets
+## Update relevant querysets
 
 If you're adding a relational field (e.g. `ForeignKey`) and intend to include the data when retrieving a list of objects, be sure to include the field using `select_related()` (for `ForeignKey` forward lookups) and/or `prefetch_related()` (for `ForeignKey` reverse lookups and `ManyToManyField` lookups) as appropriate. This will optimize the view and avoid extraneous database queries.
 
-## 5. Update API serializer
+## Update API serializer
+
+Extend the model's API serializer in `nautobot.<app>.api.serializers` to include the new field, if necessary.
 
-Extend the model's API serializer in `nautobot.<app>.api.serializers` to include the new field. In most cases, it will not be necessary to also extend the nested serializer, which produces a minimal representation of the model.
++++ 2.0.0
+Most model serializers now use `fields = [__all__]`, in which case you do not have to explicitly include the new field in the model's API serializer. The serializer will automatically pick up the field and render it according to Nautobot standards. If the default rendering does not meet your API needs, you can explicitly declare the field on the serializer.
 
-## 6. Add field to forms
+## Add field to forms
 
 Extend any forms to include the new field as appropriate. Common forms include:
 
 * **Create/edit** - Manipulating a single object
 * **Bulk edit** - Performing a change on many objects at once
-* **CSV import** - The form used when bulk importing objects in CSV format
 * **Filter** - Displays the options available for filtering a list of objects (both UI and API)
 
-## 7. Extend object filter set
+## Extend object filter set
 
 If the new field should be filterable, add it to the `FilterSet` for the model. If the field should be searchable, remember to reference it in the FilterSet's `SearchFilter` definition.
 
 All filtersets should inherit from `BaseFilterSet` or `NautobotFilterSet` as appropriate to the scope of the model's functionality.
 
-## 8. Add column to object table
+## Add column to object table
 
 If the new field will be included in the object list view, add a column to the model's table. For simple fields, adding the field name to `Meta.fields` will be sufficient. More complex fields may require declaring a custom column.
 
-## 9. Update the UI templates
+## Update the UI templates
 
 Edit the object's view template to display the new field. There may also be a custom add/edit form template that needs to be updated.
 
-## 10. Validate the new field in GraphQL
+## Validate the new field in GraphQL
 
 If the model is already part of the GraphQL schema, the new field will be included automatically. Validate that the new field is rendering properly in GraphQL. If the field is not compatible with GraphQL or shouldn't be included in GraphQL it's possible to exclude a specific field in the GraphQL Type Object associated with this specific model. You can refer to the [graphene-django documentation](https://docs.graphene-python.org/projects/django/en/latest/queries/#specifying-which-fields-to-include) for additional information.
 
 Note that if you're using the `convert_django_field` registry to override the default GraphQL representation for any field type, this override must be registered within the relevant app's `ready()` function, rather than at module import time.
 
-## 11. Create/extend test cases
+## Create/extend test cases
 
 Create or extend the relevant test cases to verify that the new field and any accompanying validation logic perform as expected. This is especially important for relational fields. Nautobot incorporates various test suites, including:
 
@@ -88,7 +86,7 @@ Create or extend the relevant test cases to verify that the new field and any ac
 
 Be diligent to ensure all of the relevant test suites are adapted or extended as necessary to test any new functionality.
 
-## 12. Update the model's documentation
+## Update the model's documentation
 
 Each model has a dedicated page in the documentation, at `models/<app>/<model>.md`. Update this file to include any relevant information about the new field.
 

nautobot/docs/development/generic-views.md

@@ -28,8 +28,6 @@ class ExampleModel(OrganizationalModel):
     name = models.CharField(max_length=20, help_text="The name of this Example.")
     number = models.IntegerField(default=100, help_text="The number of this Example.")
 
-    csv_headers = ["name", "number"]
-
     class Meta:
         ordering = ["name"]
 ```