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 documentation is a mix of legacy and contrib approaches to building SSoT integrations. We need to unify this into a clear vision and also reflect this in the import paths. We need to provide enough features to handle most of the use cases and then clearly position the set of functionality as the default.
Document how to achieve things like the primary IP (with the challenge regarding order of operations)
An open question remains whether it should also be the default for syncs from Nautobot to a remote system. It provides less benefit there (only the load method for the source adapter).
The text was updated successfully, but these errors were encountered:
Kircheneer
changed the title
Rename nautobot_ssot.contrib and promote it to the default way of building SSoT integrations.
Epic: Position contrib as the default for SSoT jobs going forward
Dec 12, 2024
Kircheneer
changed the title
Epic: Position contrib as the default for SSoT jobs going forward
Epic: Make contrib default
Dec 12, 2024
Currently, the documentation is a mix of legacy and contrib approaches to building SSoT integrations. We need to unify this into a clear vision and also reflect this in the import paths. We need to provide enough features to handle most of the use cases and then clearly position the set of functionality as the default.
Related issues:
DataMapping
and auto-populate it innautobot_ssot.contrib.NautobotAdapter
#235An open question remains whether it should also be the default for syncs from Nautobot to a remote system. It provides less benefit there (only the
load
method for the source adapter).The text was updated successfully, but these errors were encountered: