Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
DEPRECATED: remove in v14, not used anymore as of v13. We now use min_provider_version to show what providers we require.
This field contains references to other providers with the same resource/field. Note: Please do not use this field, it is only temporary and will be removed in the future once binding resources are mandatory for all executions.
Used in:
Used in:
Used in:
Canonical resource id. When a ResourceInfo is reached via an alias entry in Schema.resources, `id` is the original (aliased-to) resource name, not the alias key. Consumers that need the lookup key should use the map key from Schema.resources, not this field.
This field contains references to other providers with the same resource/field. Note: Please do not use this field, it is only temporary and will be removed in the future once binding resources are mandatory for all executions.
DEPRECATED: remove in v14, not used anymore as of v13. We now use min_provider_version to show what providers we require.
^^
Map of resource name -> resource info. Invariant: when the map key differs from the value's `id` field, the entry is an alias from the key to the resource identified by `id`. The same ResourceInfo may be referenced under multiple keys (one canonical, plus one per alias) and consumers must not assume key == value.id. The canonical name is always `value.id`. Example: `alias os.unix.sshd = sshd` produces two entries that point at the same ResourceInfo, one under "sshd" and one under "os.unix.sshd", both with `id = "sshd"`.
Resources can depend on resources from another provider, this is the list of of providers the schema depends on.
Used in: