[Bug] Challenge starts to soon using dns challenge

[tkvw]

Using a DNS challenge there needs to be time to manually setup the DNS TXT record with the provider.
As the challenge is started immediately, this fails (see the following lines).

micronaut-acme/acme/src/main/java/io/micronaut/acme/services/AcmeService.java

Lines 372 to 373 in f2d73a5

	AtomicInteger authRetryAttempts = new AtomicInteger(acmeConfiguration.getAuth().getRefreshAttempts());
	challenge.trigger();

I think this should be something in the line of:

sleep_some_initial_configured_time()
challenge.trigger()

I know there's an option to set the

auth:
   pause: 3m 

But this is only used to check the validity of the response of the challenge. I think this should be the initial delay before calling challenge.trigger

As a workaround I am currently placing a breakpoint on the challenge.trigger which allows me to setup the dns with the provider.