Update OpenSearch resource names to be relative instead of full path #4509
+67
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR updates OpenSearch resource names to use relative paths, instead of full paths, similar to how ElasticSearch does.
Motivation:
Resolve customer issue migrating from ElasticSearch to OpenSearch: #4474
Change log entry
Yes. Tracing: Update OpenSearch integration to include a feature flag for resource names. By default and with the existing implementation, the resource name is set to the full URL path; however, now resource names can instead be set to use relative paths.
Additional Notes:
How to test the change?
Tested through unit tests (
bundle exec rspec spec/datadog/tracing/contrib/opensearch/patcher_spec.rb
).