Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to store an "audit user" for changes via restAPI #18055

Open
JohannesKreuzer opened this issue Nov 21, 2024 · 0 comments
Open

Allow to store an "audit user" for changes via restAPI #18055

JohannesKreuzer opened this issue Nov 21, 2024 · 0 comments
Labels
status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application

Comments

@JohannesKreuzer
Copy link

NetBox version

v4.1.6

Feature type

Data model extension

Triage priority

N/A

Proposed functionality

allow to pass an username (actually an arbitrary string) via restAPI to store the user of the upstream application which triggered the rest api request for auditing purposes, it should default to the username of the netbox user triggering the request, if it is not passed in the request. Might be done via an additional HTTP-Header to be sent from restAPI client to netbox server.

Use case

Netbox is used as a Datasource for an upstream application. To be able to see who really triggered the changes in netbox, it is needed to be able to pass the username from the upstream application to netbox.

Database changes

add an additonal audit_username field of type string to ChangeLog model.

External dependencies

support in the netbox restAPI client libraries

@JohannesKreuzer JohannesKreuzer added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

1 participant