Use deprecated property instead of stability level

[lmolkova]

Fixes #582

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• CHANGELOG.md updated for non-trivial changes.
• schema-next.yaml

[trask]

(I moved this to "Ready to be Merged", would probably be nice to get it into upcoming release)

[marcalff]

@lmolkova

Please clarify if this causes a breaking change or not in the templates used to generate code.

In C++ for example, we use:

{%- if (attribute.stability | string()) == "StabilityLevel.DEPRECATED" %}

in here:

• https://github.com/open-telemetry/opentelemetry-cpp/blob/v1.13.0/buildscripts/semantic-convention/templates/SemanticAttributes.h.j2#L68-L70

What should that code fragment change to, once new semantic conventions are used ?

[lmolkova]

@lmolkova

Please clarify if this causes a breaking change or not in the templates used to generate code.

In C++ for example, we use:

{%- if (attribute.stability | string()) == "StabilityLevel.DEPRECATED" %}

in here:

• https://github.com/open-telemetry/opentelemetry-cpp/blob/v1.13.0/buildscripts/semantic-convention/templates/SemanticAttributes.h.j2#L68-L70

What should that code fragment change to, once new semantic conventions are used ?

yes, you're right it does cause breaking change on the jinja template side :(
Scratch that, until open-telemetry/build-tools#244 is merged and you start using the new version, this change has no effect on the tooling (which considers deprecated: descrioption and stability: deprecated to be equivalent).

Still, I'd recommend changing jinja template to do {%- if attribute.deprecated %} when updating to the upcoming version of semconv to prevent future issues.