Article deploy software packages #22245
Conversation
spokanemac
requested review from
iansltx,
lukeheath,
eashaw,
noahtalerman,
RachelElysia and
Drew-P-drawers
spokanemac
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
* Added note about fleetd 1.33 for better uninstall-on-failed-install handling * Drop load balancer call-out for batch apply now that we handle that async * Call out that software packages are managed by team, and add example use cases on why * Misc. consistency/grammar fixes (incl. overlooked oblique references to security agents) * Clarify side effects on package edit/remove * Call out that when managing via GitOps the Fleet server, not the GitOps runner, is the one to pull packages, in case people need to set their firewalls accordingly * Bump publish date since this is basically a fresh guide with URL backward compat
|
So, we have a few broken learn-more links. There are two in the article, and they're also referenced in the advanced package options dialog on edit software as of this release. There's also a broken learn-more-about link for EXE installers in particular. Current plan:
The above is forward-compatible with dedicated articles/docs on these items, and provides sufficient information in the interim IMO. ETA for all of the above is later this evening. Will ping when it's ready. |
…ame, expand install advanced options into headings
…ription in deploy-software-packages article
|
Found another broken learn-more-about link, so pointed that at this article as well. We probably want to revisit whether we have these links, and where they go to, but at least this way they don't 404. |
|
Okay, now everything's ready, I think. |
|
^ @spokanemac ping me if any of these edits don't make sense, given that there are a bunch of them. |
spokanemac
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
Article: Guide update deploy software packages #21841