[8.19] (backport #11826) Fix signature verification using the upgrade command with the --source-uri flag for fleet-managed agents #11975
+190
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fix PGP verification to use the .asc file located in the dir specified by --source-uri when upgrading a fleet-managed agent.
Why is it important?
Upgrading using a local source currently requires a work-around.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature works./changelog/fragmentsusing the changelog toolDisruptive User Impact
N/A
Related issues
file://source URI to upgrade from a local directory, Elastic Agent does not fetch the .asc from the source URI #11152This is an automatic backport of pull request Fix signature verification using the upgrade command with the --source-uri flag for fleet-managed agents #11826 done by Mergify.