[chore] Update CODEOWNERS and bring oracle cloud metadata up to standards #46006
+79
−38
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.
Description
Discussed with @dashpole and now that I am a codeowner for the oraclecloud area in the semconv repo, I am requesting codeowner status in collector-contrib as well.
Required "Ride-Along" Fixes
Making changes to
metadata.yamlrequires regenerating some files withmdatagen, which requires some further changes for the generating process itself to work. Seems that some standards have changed over the past few months, and themetadata.yamlfile was no longer up to spec. When I tried to runmdatagen metadata.yamlI got an error:Just as @paulojmdias discovered in a similar PR I also needed to make some changes to
metadata.yamlto follow the conventions of some (but confusingly not all) other resource detection processors. I've followed suit by making similar changes in this PR, and nowmdatagencleanly generates files.Also, somehow the descriptions for the attributes had been replaced with non-descriptive descriptions at some point recently, so I am restoring them.
Testing
Ran
mdatagensuccessfully.