Add support for application config -> matchspecification -> entity?

[karamelba]

Hi, i'd like to understand how to set the entity ('Destination' or 'Source') within the matchspecification of an application configuration.
The Instana APi https://instana.github.io/openapi/#operation/addApplicationConfig marks the field 'entity' as required.
If i create a match specification like 'kubernetes.namespace EQUALS 'xyz' via the terraform-provider-instana, the result is an application config with a match specification of type 'Destination'.
How can i achieve a match specification of type 'Source'?
Thanks a lot!

[gessnerfl]

@karamelba: this is currently not supported. I marked the ticket as a feature and will check how this can be supported

[karamelba]

Great! Thank you :-)

[gessnerfl]

I will adjust the match expression syntax such as that you can optionally specify the entity origin (source or destination) after the entity path. For compatibility it will be defaulted to destination when the origin is omitted.

Examples:

entity.name      # no entity origin specified -> defaults to destination
entity.name@src  # entity name at the source of the call
entity.name@dest # entity name at the destination of the call

[karamelba]

Sounds great! :-)

[gessnerfl]

Defaulting to destination is not a valid approach. There are entities which do not support source or destination. Will check if the API is defaulting the values properly. In the API entity is marked as required but this does not implemented like this.

[gessnerfl]

Feature is available with version 0.10.0

[karamelba]

Thanks a lot for this enhancement!