You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the app requires access to an email account to discover emails, but this is not always available or desired. We should provide a Job that can be called via API with all required parameters needed (provider, raw email, etc) to attempt to create all applicable Nautobot objects (maintenance, circuits impacted, etc).
Use Case
I don't use IMAP or GMail for my mail provider
My Nautobot instance cannot be provided access to the internet or given any email credentials to poll an inbox
The text was updated successfully, but these errors were encountered:
@joewesch , I think #282 is related, but here, I understand that you want to expose via a very simple job a parsing strategy to call on-demand externally. isn't it?
Yes, it is related in the same sense of trying to bypass needing the app itself to monitor a mailbox. I have a client that would like to be able to parse the inbox externally (their Nautobot instance doesn't have access to much) and send the contents to the circuit maintenance app via API call. My initial thought was a Job, but there may be other/better methods that could suffice.
Probably could be done directly as a custom REST API endpoint (something like /api/plugins/circuit-maintenance/raw-notifications/parse/ perhaps?) without needing a Job per se.
Proposed Functionality
Currently the app requires access to an email account to discover emails, but this is not always available or desired. We should provide a Job that can be called via API with all required parameters needed (provider, raw email, etc) to attempt to create all applicable Nautobot objects (maintenance, circuits impacted, etc).
Use Case
The text was updated successfully, but these errors were encountered: