Skip to content

[CONFIGURATION] File configuration - misc model #3504

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

marcalff
Copy link
Member

Contributes to #2481

This is a partial fix, that implements supporting declarations.

Changes

Please provide a brief description of the changes here.

  • Implement the miscellaneous model for file configuration.

For significant contributions please make sure you have completed the following items:

  • CHANGELOG.md updated for non-trivial changes
  • Unit tests have been added
  • Changes in public API reviewed

@marcalff marcalff requested a review from a team as a code owner June 28, 2025 23:38
Copy link

netlify bot commented Jun 28, 2025

Deploy Preview for opentelemetry-cpp-api-docs canceled.

Name Link
🔨 Latest commit 59d6a3b
🔍 Latest deploy log https://app.netlify.com/projects/opentelemetry-cpp-api-docs/deploys/68607cfd1d1477000871e22a

Copy link

codecov bot commented Jun 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.94%. Comparing base (f16ea3b) to head (59d6a3b).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #3504      +/-   ##
==========================================
- Coverage   89.96%   89.94%   -0.02%     
==========================================
  Files         219      219              
  Lines        7051     7051              
==========================================
- Hits         6343     6341       -2     
- Misses        708      710       +2     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


#pragma once

#include <map>
Copy link
Contributor

Choose a reason for hiding this comment

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

map can be removed.

namespace configuration
{

enum enum_otlp_http_encoding : std::uint8_t
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider adding a comment indicating the intended deviation from the style guide. Perhaps link to this #3467 (comment)?


#pragma once

#include <map>
Copy link
Contributor

Choose a reason for hiding this comment

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

map can be removed

std::unique_ptr<AttributesConfiguration> attributes;
std::unique_ptr<DetectorsConfiguration> detectors;
std::string schema_url;
std::string attributes_list;
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a required notation for the string of attributes? "key=value;..." ?


// YAML-SCHEMA: schema/resource.json
// YAML-NODE: AttributeNameValue
// FIXME: Name/Value/Type
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you share more on the FIXME's? Will these be addressed in later PRs as part of the initial roll out of the yaml configuration feature or left for a later phase?

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.

2 participants