Matthijs Mekking 68e9603ed8 Test keymgr2kasp state from timing metadata ... Add two test zones that migrate to dnssec-policy. Test if the key states are set accordingly given the timing metadata. The rumoured.kasp zone has its Publish/Active/SyncPublish times set not too long ago so the key states should be set to RUMOURED. The omnipresent.kasp zone has its Publish/Active/SyncPublish times set long enough to set the key states to OMNIPRESENT. Slightly change the init_migration_keys function to set the key lifetime to "none" (legacy keys don't have lifetime). Then in the test case set the expected key lifetime explicitly. (cherry picked from commit c40c1ebcb1)		2021-03-22 11:24:55 +01:00
..
kasp.conf.in	Test keymgr2kasp state from timing metadata	2021-03-22 11:24:55 +01:00
named.conf.in	Test keymgr2kasp state from timing metadata	2021-03-22 11:24:55 +01:00
named2.conf.in	Test keymgr2kasp state from timing metadata	2021-03-22 11:24:55 +01:00
setup.sh	Test keymgr2kasp state from timing metadata	2021-03-22 11:24:55 +01:00
template.db.in	Move kasp migration tests to different directory	2021-03-22 11:24:55 +01:00