Branching feature should work with NetBox database objects deployed under user defined schema (not public).

[sawantmg]

Plugin Version

netbox-branching Release v0.5.2

Proposed functionality

With the branching feature, when a local branch is activated, the search_path option in the connection string is updated to include the schema associated with the 'activated branch' as the first choice, followed by the 'public' schema. However, this doesn't well work if the NetBox database objects are deployed under the 'public' schema. Access to any object that is not part of the 'activate branch' fails as that object cannot be found under the 'public' schema either.

Please update the functionality such that the branching feature works with an user defined schema.

Use case

With managed databases, users may not be able to deploy application specific database objects to public schema. Therefore, it is important for NetBox branching feature to support user defined schemas.

External dependencies

No response

[jeremystretch]

@sawantmg I'm not sure I follow:

However, this doesn't well work if the NetBox database objects are deployed under the 'public' schema.

Did you mean objects that are not in the public schema? Is the proposal here just to allow the NetBox administrator to configure the name of the default PostgreSQL schema?

[sawantmg]

Correct.