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

Epic: Make contrib default #630

Open
1 of 6 tasks
Kircheneer opened this issue Dec 12, 2024 · 0 comments
Open
1 of 6 tasks

Epic: Make contrib default #630

Kircheneer opened this issue Dec 12, 2024 · 0 comments
Labels

Comments

@Kircheneer
Copy link
Contributor

Kircheneer commented 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:

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).

@Kircheneer Kircheneer added status: accepted This issue has been accepted by the maintainers team for implementation integration: contrib Contrib related issues and PRs labels Dec 12, 2024
@Kircheneer 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 Kircheneer changed the title Epic: Position contrib as the default for SSoT jobs going forward Epic: Make contrib default Dec 12, 2024
@Kircheneer Kircheneer added epic and removed status: accepted This issue has been accepted by the maintainers team for implementation integration: contrib Contrib related issues and PRs labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant