Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Lime ¶
func (*Lime) SaveContact ¶
SaveContact upserts a contact matched by (source, source_id) rather than by factum ID - same reason as SaveCustomer. NotifyMaintenance is factum-owned (the operator toggle on the contacts page, including for Lime-synced rows) so a resync must not reset it; new Lime persons default it to false so they are not mailed until an operator opts them in.
func (*Lime) SaveCustomer ¶
SaveCustomer upserts a customer matched by (source, source_id) rather than by factum ID - the factum ID is autogenerated (see SyncCustomers) so it can't be used to find a previously-synced row. Lime-owned fields are copied onto the existing row so a resync does not zero CreatedAt (GORM Save writes the whole struct, including zero timestamps).
func (*Lime) SaveDelivery ¶
SaveDelivery upserts a service matched by (source, source_id) rather than by factum ID - the factum ID is autogenerated (see SyncCustomers) so it can't be used to find a previously-synced row.
Lime never feeds ServiceType/BandwidthMbps/MaxMacAddresses, Fields, PseudowireID, L2VPNNetboxID or connection_type_id - those are only ever set from the factum side. Overlaying Lime-owned fields onto the stored row (instead of Save() of a fresh struct) keeps a resync from wiping that enrichment and from zeroing CreatedAt. service_endpoints is a separate table and is not touched.