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

Provide Scripts/Reports a feature to standardize send_email output #7790

New Issue
Closed
opened 2025-12-29 20:28:15 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:28:15 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Mar 23, 2023).

NetBox version

v3.4.6

Feature type

New functionality

Proposed functionality

As stated in the documents, you can setup send_mail in the configuration. It would be nice to add an additional feature to:

  1. Enable automatic email of "job" (script and email) completion - should be a boolean sort of like commit
  2. Provide a message variable where you can feed it markdown, but if not set would the email message to send the script/report summary table (already rendered in netbox) and a link to the specific report job results.

Use case

Remove the barrier to entry for users creating reports and scripts that want to fire off emails.

Database changes

None

External dependencies

None

Originally created by @ryanmerolle on GitHub (Mar 23, 2023). ### NetBox version v3.4.6 ### Feature type New functionality ### Proposed functionality As stated in the documents, you can setup send_mail in the configuration. It would be nice to add an additional feature to: 1. Enable automatic email of "job" (script and email) completion - should be a boolean sort of like `commit` 2. Provide a message variable where you can feed it markdown, but if not set would the email message to send the script/report summary table (already rendered in netbox) and a link to the specific report job results. ### Use case Remove the barrier to entry for users creating reports and scripts that want to fire off emails. ### Database changes None ### External dependencies None
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:28:15 +01:00
adam closed this issue 2025-12-29 20:28:15 +01:00
adam commented 2025-12-29 20:28:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 3, 2023):

@ryanmerolle could you expand the above to include a mock-up of the proposed implementation? I think the fundamental functionality is clear but I'd like to see some discussion around a concrete implementation. Thanks!

@jeremystretch commented on GitHub (Apr 3, 2023): @ryanmerolle could you expand the above to include a mock-up of the proposed implementation? I think the fundamental functionality is clear but I'd like to see some discussion around a concrete implementation. Thanks!
adam commented 2025-12-29 20:28:16 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 3, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 3, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:28:16 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 2, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Aug 2, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review 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#7790
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?