Describe the feature:
The elastic-agent CLI accepts file:// URIs as --source-uri parameter and works pretty well with it, so Fleet should allow adding URIs of that type as agent binary sources too.
Describe a specific use case for the feature:
Upgrading agents that have restricted access to the internet can be done seamlessly if this feature is implemented. Currently one can trigger an upgrade on a host by providing the file and the sha signature, but when the agent tries to talk back to the Fleet server, it rejects the new version as seen here. Allowing the file URI would allow uploading the necessary files to the hosts, and triggering the upgrade from the Fleet.
Describe the feature: The
elastic-agent
CLI acceptsfile://
URIs as--source-uri
parameter and works pretty well with it, so Fleet should allow adding URIs of that type as agent binary sources too.Describe a specific use case for the feature: Upgrading agents that have restricted access to the internet can be done seamlessly if this feature is implemented. Currently one can trigger an upgrade on a host by providing the file and the sha signature, but when the agent tries to talk back to the Fleet server, it rejects the new version as seen here. Allowing the file URI would allow uploading the necessary files to the hosts, and triggering the upgrade from the Fleet.