Resource conventions: Many ambiguities

[kbrockhoff]

In the existing Resource attributes names currently appear to be sufficient to cover most use cases. However, there are many ambiguities around which attributes should be populated for a particular use case and what system property should supply the value.

There are multiple facets to this. For example, some attribute types have a required column while others don't. At least one other open issue highlights a specific item within the overall problem. #559

In order to ensure consistent implementation across all of the officially supported SDKs, I propose adding a matrix with attributes on one axis and deployment environments on the other, specifying whether an attribute should be populated and exactly where the value should be obtained from if it is populated.

[tigrannajaryan]

I think consistency is at least partially solved by YAML generator. Do we still need this and is it a must-have for GA?

[andrewhsu]

@kbrockhoff from the issue triage mtg today, trying to bucket issues that can be addressed after GA. if you don't have more info on this by 2020-09-10, this issue will be moved to after-ga.

[kbrockhoff]

I envision this as documentation explaining the specification. This can easily be after-ga

[carlosalberto]

@kbrockhoff Thanks!