DNSSEC-Provisioning / DNSSEC-Provisioning/music
Need a more flexible stop-reason system to handle the wait-for-ds issue
Open
- Dominant language
- Go
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Progress is not "blocked", it is only "delayed" and we know for how long. So the FSM Engine should understand to check if the zone is just delayed and then look at the current time to see if it is possible to progress or not.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.