-
Notifications
You must be signed in to change notification settings - Fork 151
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 manifest to package #3910
Add manifest to package #3910
Conversation
This pull request does not have a backport label. Could you fix it @pchila? 🙏
NOTE: |
aeca3a3
to
cc0398b
Compare
cc0398b
to
9e6c04f
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
9e6c04f
to
f90a1d1
Compare
d202cc9
to
39de109
Compare
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
Looks good.
buildkite test this |
a2b55cf
to
e9a2b30
Compare
@@ -19,11 +20,13 @@ import ( | |||
|
|||
"golang.org/x/text/cases" | |||
"golang.org/x/text/language" | |||
"gopkg.in/yaml.v3" | |||
|
|||
"github.com/magefile/mage/sh" | |||
"golang.org/x/tools/go/vcs" |
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.
Created dedicated issue for vcs removal #4138
44766ec
to
1ddae31
Compare
This could have a changelog, it could also just be referenced in #3950. This is not strictly user facing, but it is something support will want to know exists. |
I checked this out and built it, it seems to require me to clean out the contents of
That is a failure trying to verify a windows package I built prior to this change. I think this is fine, just requires an FYI to people that they are likely to hit this after this merges. |
Can you add some documentation on what the manifest file is and how it gets used? If it only makes sense to do this after #3950 that is fine, but it should be documented somewhere in the repository itself. |
1ddae31
to
aec6b0c
Compare
@cmacknz Regarding the package test failure, I am assuming (and checking) in the package tests that the manifest file is present and contains valid information. As for documentation, I will probably add something in #3950 since I have to document also how the upgrade works with the manifest and the remapping |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
What does this PR do?
This PR adds a manifest to .zip, tar.gz, .deb and .rpm packages according to the outcome of #3639
In this PR the manifest is only generated and included in the packages but not yet used by install or upgrade processes.
Why is it important?
This is a prerequisite for #3950 where the manifest included in the package will be used for remapping package directories during install and upgrade
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry in./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testAuthor's Checklist
How to test this PR locally
It can be interesting having a look at .tar.gz or .zip packages and see how the manifest content (especially path mappings) changes when specifying different versions from the same commit for example:
and
Related issues
Use cases
Screenshots
Logs
Questions to ask yourself