dnsresource with the
humanitec/dns-cloudflaredriver requires the Cloudflare Zone ID and the parent domain to be specified while the
humanitec/dns-wildcarddriver only requires the parent domain.
dnsand given it the ID
api-dns. (This makes its fully qualified resource ID
shared.api-dns.) If there are three environments (
production) then there will be three instances of this resource - one in each environment. Each active resource will have the same Application ID and Resource ID, but they will have different Environment IDs. Therefore they each have a unique context:
Environment IDwould score 4 and one containing an
Environment Typewould score 3.
awesome-appwith multiple Environments of type
development. There is a shared environment called
devused by all developers and multiple "PR" environments which are created automatically when a PR is created in GitHub. The
devenvironment should be accessible via a stable DNS name of
dev-api.awesome.appwhile the preview environments should be available on randomly generated subdomains such as
static-dev-dns- always returns the same DNS name of
random-dev-dns- generates a random subdomain
devenvironment, Humanitec will attempt to provision a
dnsresource with ID
shared-api-dns. Looking at the matching criteria for Resource Definitions of type
dnsit will return
random-dev-dns. In this case, the
static-dev-dnswould be chosen because it's Matching Criteria is more specific.
random-dev-dnsResource Definition would be returned.