Closed pacamaster closed 1 month ago
@lukeheath @georgekarrv , this looks to me like similar area to what we do so I applied EOPs label. Feel free to change to MDM.
@sharon-fdm This is actually software self-service (uploading your own packages), which the MDM group built so I'm sending this their way.
@pacamaster This is expected behavior. The current workflow is to first delete the package before uploading a new one. I agree it feels buggy from a UX perspective, so I'm going to send this bug to the drafting board for designers to review the workflow.
When trying to upload packages for cloudflareWARP, unable to do different versions or update to new version. Need to delete and remove from Fleet to upload a new one
Hey @pacamaster this is the current expected, frustrating behavior.
I confirmed w/ the customer that what we're planning on building in the "Edit software" (#20404) story will satisfy the workflow described in this issue.
See the Slack thread here (internal).
Closing this issue.
cc @Patagonia121 @lukeheath @sharon-fdm
With each update's dawn, Fleet adapts, like clouds in flight. No app left forlorn.
Fleet version: <!-- Copy this from the "My account" page in the Fleet UI, or run
fleetctl --version
--> 4.54.1 Web browser and operating system: Current browser and OS💥 Actual behavior
When trying to upload packages for cloudflareWARP, unable to do different versions or update to new version. Need to delete and remove from Fleet to upload a new one
🧑💻 Steps to reproduce
🕯️ More info (optional)
Believe might be due to the versioning of this package not being directly included. Cloudflare does it in the filename. The default behavior should be to keep the existing software and associate a new package. Packages do not exactly equal apps.