Reintroduce nautobot.setup()
function
#5532
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #5531
What's Changed
In #5310 I removed the
nautobot.setup()
function as part of refactoring, not realizing that there were outside use cases relying on it. This resulted in:pylint --init-hook "import nautobot; nautobot.setup()" ...
)nautobot.setup()
to be able to run Nautobot/Django code to create a default user)This PR reintroduces a form of this function that works similarly but keeps the startup-sequence refactoring from #5310 in place otherwise.
As a bonus, we can adopt the same pattern used in Apps to run pylint, i.e.
pylint --init-hook "import nautobot; nautobot.setup()" ...
and therefore no longer have a need for the hackishnautobot-server pylint
command that we'd added to theexample_app
as a workaround.Screenshots
TODO