add initial options for SDK configuration

[codeboten]

These options include disabled and resource.attributes.

Will rebase after #13 is merged

[jack-berg]

Suggested change

	service:
	# Sets the value of the `service.name` resource attribute
	#
	# Environment variable: OTEL_SERVICE_NAME
	name: "unknown_service"
	# Sets the value of the `service.name` resource attribute
	#
	# Environment variable: OTEL_SERVICE_NAME
	service:\name: "unknown_service"

attributes as a flat map of key values for now.

Should consider whether the value's type is unambiguous. For example, if the attribute is key: 10 does 10 map to a string, integer, or float? Alternatively could do something like:

attributes:
  -  key: service.name
      string_value: "unknown_service"
  - key: foo
     int_value: 10

More verbose yes, but also unambiguous which would address issues like this.

[codeboten]

So yaml supports !!int to force a type, any thoughts on using that instead of having different field identifier for the different types?

I guess having different field identifiers would allow us to support lists/arrays more easily in the future.

[jack-berg]

So yaml supports !!int to force a type

Didn't realize that!

Suppose that provides an answer for list / arrays as well (i.e. [!!int 10, !!int 15]) but not super pretty. This alleviates most of my concern. Happy enough going with a service.name: value for now. Either way, I'm sure this won't be the last time it comes up 😁