-
Notifications
You must be signed in to change notification settings - Fork 490
Remove duplicated fields #3316
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
Remove duplicated fields #3316
Conversation
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
🌐 Coverage report
|
| cloud.project.id | Name of the project in Google Cloud. | keyword | | ||
| cloud.provider | Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean. | keyword | | ||
| cloud.region | Region in which this host is running. | keyword | | ||
| container.id | Unique container id. | keyword | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't expect any adds or removes in the READMEs, only modifications to descriptions or types due to the duplicate removal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adds are going to happen, because of elastic/elastic-package#814, we were installing fields that were not documented.
But yes, removals shouldn't happen. There are still some other things I have to polish here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrewkroh at the end having adds and removes was a a good indicator that something was wrong 🙂
We are delaying removal of duplicated fields till we clarify some issues (elastic/package-spec#331) closing this by now. |
What does this PR do?
Remove duplicated fields.
This is important to avoid unexpected results, when definitions are different any of them could be applied.
This is also a requirement to use package-spec 1.8.0.
See elastic/package-spec#309.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots