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 CI testing for metadata.yaml #23335

Closed
2 tasks
mackjmr opened this issue Jun 13, 2023 · 4 comments
Closed
2 tasks

Add CI testing for metadata.yaml #23335

mackjmr opened this issue Jun 13, 2023 · 4 comments
Assignees

Comments

@mackjmr
Copy link
Member

mackjmr commented Jun 13, 2023

Component(s)

cmd/mdatagen

Describe the issue you're reporting

Now that the following issue is done, we have a metadata.yaml file for all components.

This is a proposal to add a CI test to validate certain aspects of the metadata.yaml. I have separated this in two parts, one for all components, and one specific to receivers (for which the proposal has additional checks):

Note:

@mackjmr mackjmr added the needs triage New item requiring triage label Jun 13, 2023
@github-actions github-actions bot added the cmd/mdatagen mdatagen command label Jun 13, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@songy23 songy23 removed the needs triage New item requiring triage label Jun 13, 2023
@mackjmr mackjmr changed the title Add CI test to check metadata.yaml for all components. Add CI testing for metadata.yaml Jun 14, 2023
@mackjmr
Copy link
Member Author

mackjmr commented Jun 14, 2023

Update: I've separated this issue into 2 sub issues (linked in the checkbox) -- 1 for all components, and one specific to receivers.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Aug 14, 2023
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants