starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Don't cache openapi schema when debug/insecure mode is enabled #10478

New Issue
Closed
opened 2025-12-29 21:32:01 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:32:01 +01:00
Owner
Copy Link

Originally created by @prryplatypus on GitHub (Nov 15, 2024).

NetBox version

v4.1.4

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

When debug mode or Django --insecure mode is enabled, the OpenAPI schema shouldn't be cached (or the cache should be busted upon reload/restart).

Use case

When developing plugins, it is common that the schema is changed. Having to bust this cache manually every time a change is made in development is additional unnecessary work the the developer, which hinders DX and in cases confuses the developer wondering why changes aren't showing.

Database changes

No response

External dependencies

No response

Originally created by @prryplatypus on GitHub (Nov 15, 2024). ### NetBox version v4.1.4 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality When debug mode or Django `--insecure` mode is enabled, the OpenAPI schema shouldn't be cached (or the cache should be busted upon reload/restart). ### Use case When developing plugins, it is common that the schema is changed. Having to bust this cache manually every time a change is made in development is additional unnecessary work the the developer, which hinders DX and in cases confuses the developer wondering why changes aren't showing. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:32:01 +01:00
adam closed this issue 2025-12-29 21:32:01 +01:00
adam commented 2025-12-29 21:32:01 +01:00
Author
Owner
Copy Link

@prryplatypus commented on GitHub (Nov 15, 2024):

Will not be needed when #18021 is fixed

@prryplatypus commented on GitHub (Nov 15, 2024): Will not be needed when #18021 is fixed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10478
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?