-
Notifications
You must be signed in to change notification settings - Fork 118
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 howto about migrating a package to package spec v2 #964
Add howto about migrating a package to package spec v2 #964
Conversation
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.
LGTM
And those examples with possible errors will help for sure developers to upgrade the packages from v1 to v2 👍
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
@v1v It looks like the job is still being triggered by beats-ci? |
Version of the Package Spec used by a package is defined by the `format_version` | ||
setting in the `manifest.yml` file. | ||
|
||
## Upgrading from Package Spec v1 to v2 |
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.
nit: I would add a prefix "Troubleshooting" as this is rather information about how to fix an issue.
🌐 Coverage report
|
Failure is unrelated, merging. |
Add documentation about how to solve validation issues found with packages following the package spec v2.
Part of elastic/package-spec#399.
Fixes #963 (additional implemented validations should include their own docs in this document).