Open dantecatalfamo opened 2 weeks ago
Thanks for tracking this one @dantecatalfamo.
Do you know of other CLI tools with similar flags? I think we want a solution that's consistent w/ other tools.
Removing ~engineering-initiated
from this story because there are product changes. We'll weigh this at the next feature fest on 2024-06-20.
Problem
As a developer, we often have to create multiple versions of the fleet installer to cover difference scenarios, like with or without a custom TUF server, the base fleet installer without secrets for Azure installation, creating an installer with or without scripts enabled, etc.
The current behaviour is that every time you generate a new installer,
fleetctl
will overwrite the one you've generated previously, even if it was built with different parameters. This can make it difficult to export several versions at once.Potential solutions
Add an output parameter to
fleetctl package
. This could come in the form of-o
or--output
for specifying the full name, or a sort of--postfix
argument that makesfleetctl package
append a custom string to the end of the installer filename.