Prevents a double warning showing if you have mTLS disabled and no mTLS related policies.
Before
After
~I've also pinned kongponents version to the same version as release-2.8 to prevent it automatically moving forwards when to the version we have on master~
We don't actually need to do the crossed out kongponents pin, its again another consequence of other dependencies unnecessarily bumping kongponents in their package.json file.
What we do need to do is use a version of app-layout that has a minimum kongponents version that has a constraint that includes our version of kongponents in release-2.8, which is why I've chosen 4.2.3
Prevents a double warning showing if you have mTLS disabled and no mTLS related policies.
Before
After
~I've also pinned kongponents version to the same version as release-2.8 to prevent it automatically moving forwards when to the version we have on
master~We don't actually need to do the crossed out kongponents pin, its again another consequence of other dependencies unnecessarily bumping kongponents in their package.json file.
What we do need to do is use a version of app-layout that has a minimum kongponents version that has a constraint that includes our version of kongponents in release-2.8, which is why I've chosen 4.2.3