* Avoid using "infrastructure" terminology for all cloud
Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
termilogy because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.
Renaming "infrastructure_service" to "service" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.
* Explicitly specify cloud.provider values for common cloud providers
Before some cloud provider values were given as an examples but it was still
left open to interpretation about what that meant. This makes it more explicit
that these are known values for those particular cloud providers.
* Apply suggestions from code review
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Jaana Dogan