Component
API Server / GraphQL
Infrahub version
1.7.6
Current Behavior
Let's say we have a prefix 10.1.1.0/24 whose current parent is 10.0.0.0/8. Now, If a new prefix 10.1.0.0/16 is added to main, it will break any existing branches in infrahub as they cannot be merged due to a conflict.
There is no way to solve this conflict in infrahub.
Expected Behavior
Expect the rebase operation to take care of this change in hierarchy automatically.
Steps to Reproduce
same as the issue description
Additional Information
No response
Component
API Server / GraphQL
Infrahub version
1.7.6
Current Behavior
Let's say we have a prefix 10.1.1.0/24 whose current parent is 10.0.0.0/8. Now, If a new prefix 10.1.0.0/16 is added to main, it will break any existing branches in infrahub as they cannot be merged due to a conflict.
There is no way to solve this conflict in infrahub.
Expected Behavior
Expect the rebase operation to take care of this change in hierarchy automatically.
Steps to Reproduce
same as the issue description
Additional Information
No response