These are visual studio code's workspace configuration files.

The mock acme authority needs to in order to conform to the updated acme
authority interface.

Makes the line more readable.

Section 8.2 of RFC 8555 explains how retries apply to the validation
process. However, much is left up to the implementer.

Add retries every 12 seconds for 2 minutes after a client requests a
validation. The challenge status remains "processing" indefinitely until
a distinct conclusion is reached. This allows a client to continually
re-request a validation by sending a post-get to the challenge resource
until the process fails or succeeds.

Challenges in the processing state include information about why a
validation did not complete in the error field. The server also includes
a Retry-After header to help clients and servers coordinate.

Retries are inherently stateful because they're part of the public API.
When running step-ca in a highly available setup with replicas, care
must be taken to maintain a persistent identifier for each instance
"slot". In kubernetes, this implies a *stateful set*.

The comment in acme/authority directs users to this file so put a TODO
in for posterity.

It might make sense to check in the vscode workspace file if we can make
everything relative to the project directory.

Stop execution when the error happens. This was previously a typo.

Prior to validation, we must wrap the base challenge in the correct
concrete challenge type so that we dispatch the correct validation
method.

When cloning a challenge, deeply clone the retry field if it is not nil.

In golang, one should always return error types rather than interfaces
that conform to an error protocol. Why? Because of this:

    https://play.golang.org/p/MVa5vowuNRo

Feels ~~like JavaScript~~ bad, man.

Remove superfluous test. Add test checking for the Retry-After header if
the challenge's RetryAfter field is set.

* Add toACME test for the "processing" state.

The comment appeared too early.

The mock has an old func that is no longer used. Remove it.

The linter likes comments on public functions to start with their name,
for some reason...

Include the "Link" and "Location" headers on invalid challenge
resources. An invalid challenge is still a perfectly acceptable
response.

The error message was updated. Make the test should reflect the new
changes.

Also, return early from ValidateChallenge if the challenge is already
valid. Interestingly, we aren't actually testing most of the
ValidateChallenge func, just the early error and return conditions. We
should add some more coverage here.

On the challenge resource, set "Link" and "Location" headers for all
successful requests to the challenge resource.

The authority now receives the ordinal in its constructor rather than a
global variable set at package initialization time. The ordinal is
passed via the command line option `--ordinal`.

Since it will ultimately 500 anyway, just return an error.

Add tests for the starting challenge statuses.
Removed unneeded db write test.

This logic was already in the correct form so it was much easier to
update.

Add `golanglint-ci` to the modules so it's available when running `make
lint`.