pmprado
pmprado
> So schema should be relaxed to not enforce uniqueness on primary key and then we need to ensure we use `append_if_unique` in the code. Makes sense - I take...
> Reclassifying it as this is historic behavior and changing it this way. For several minor releases we have been introducing this kind of behavior in other areas of AVD...
> If you only want an l2vlan, you should use that model instead. Absolutely, but on this case I need the l2vlan on some switches and the svi on others....
> Review docs on [Read the Docs](https://ansible-avd--4050.org.readthedocs.build/en/4050/) > > To test this pull request: > > ```shell > # Create virtual environment for this testing below the current directory >...
I've tested it and it does not warn anymore for when we have repeated IPs across devices. It builds correctly. However, shouldn't it warn on this? In my testing it...
> This code should not allow duplicates. Have you tested? Your example above had the same exact info twice. Such duplication is silently ignored. Only one peering will be added...
The tech-library is recommending to use the `vxlan-v6-underlay` TCAM profile now. Should we review this?
@MaheshGSLAB Supported in the latest release already
> It was not supported when the comment was added. Guillaume > […](#) > On Thu 7 Nov 2024 at 19:12, pmprado ***@***.***> wrote: @MaheshGSLAB Supported in the latest release...