Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add schema_url attribute to Resource #17

Closed
wants to merge 13 commits into from
Closed

Conversation

dgetu
Copy link

@dgetu dgetu commented May 22, 2021

A change in the OTel specification requires a new schema_url field in the Resource class. This change modifies tests which used the old constructor signature.

Type of change

  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

All tox tests were ran on Python 3.9. One test was modified to account for the change in constructor signature.

Does This PR Require a Contrib Repo Change?

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated - The documentation doesn't reference the method headers, so there's no update to the documentation.

@dgetu dgetu marked this pull request as ready for review May 24, 2021 23:34
@dgetu dgetu requested a review from alolita May 24, 2021 23:34
CHANGELOG.md Outdated
@@ -8,6 +8,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

- Fixed cases where description was used with non-error status code when creating Status objects.
([#504](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/504))
### Changed
- Added optional `schema_url` field to `Resource` class
([opentelemetry-python #1862](https://github.com/open-telemetry/opentelemetry-python/issues/1862))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copied from my comment in the core PR

By the way, this should be the number and link to the PR you submit on the upstream repo. Since you usually wouldn't have submitted it yet, you could just put TBD here until you submit to upstream. Or, you could also use the one you accidentally opened/closed and re-open that PR 😄

@dgetu dgetu closed this May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants