- We're adding an option to filter the activity feed on the dashboard,
and we introduced a dropdown to filter by activity type. We want to use
more human friendly names.
e.g. `edited_macos_min_version` -> "OS updates: edited macOS"
---------
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
* Updated MySQL instructions to use `bitnamilegacy/mysql`
* Updated Redis Instructions to use `bitnamilegacy/redis`
---------
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
This is a quick fix to handle all three cases when showing the unenroll
modal for ios and ipad devices.
It also adds better naming to the functions that check the enrollment
type.
- [x] QA'd all new/changed functionality manually
Add link to reach out to sales
- Context: Folks from Microsoft are going to create a LinkedIn post
talking about Entra conditional access. They're going to link to this
guide in the LinkedIn post.
**Related issue:** Resolves#33695
When trying to match package icons, first try to match by hash then by
URL.
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [X] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.
## Testing
- [X] QA'd all new/changed functionality manually
---------
Co-authored-by: Ian Littman <iansltx@gmail.com>
<!-- Add the related story/sub-task/bug number, like Resolves#123, or
remove if NA -->
**Related issue:** Resolves#33698
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.
- [x] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [x] If paths of existing endpoints are modified without backwards
compatibility, checked the frontend/CLI for any necessary changes
## Testing
- [x] Added/updated automated tests
- [x] Where appropriate, [automated tests simulate multiple hosts and
test for host
isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing)
(updates to one hosts's records do not affect another)
- [x] QA'd all new/changed functionality manually
<!-- Add the related story/sub-task/bug number, like Resolves#123, or
remove if NA -->
**Related issue:** Resolves#33492
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] If paths of existing endpoints are modified without backwards
compatibility, checked the frontend/CLI for any necessary changes
## Testing
- [x] Added/updated automated tests
- [ ] Where appropriate, [automated tests simulate multiple hosts and
test for host
isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing)
(updates to one hosts's records do not affect another)
- [x] QA'd all new/changed functionality manually
For unreleased bug fixes in a release candidate, one of:
- [ ] Confirmed that the fix is not expected to adversely impact load
test results
- [ ] Alerted the release DRI if additional load testing is needed
- Added additional platform information to address confusion encountered
during a recent prospect call.
---------
Co-authored-by: Rachael Shaw <r@rachael.wtf>
Add Cloud Computing Policy to the Handbook. Customers have required this
to be in our Policy.
Verified that the policy is rendered correctly and consistent with the
style in the handbook.
No Issue creates as this is just a documentation change to the policy.
---------
Signed-off-by: Ram Marti <ram@fleetdm.com>
Co-authored-by: Ram Marti <ram@fleetdm.com>
Co-authored-by: Luke Heath <luke@fleetdm.com>
Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
Fixes a miss in #31464.
## Testing
- [ ] QA'd all new/changed functionality manually
For unreleased bug fixes in a release candidate, one of:
- [x] Confirmed that the fix is not expected to adversely impact load
test results
<!-- Add the related story/sub-task/bug number, like Resolves#123, or
remove if NA -->
**Related issue:** Resolves#32432
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.
## Testing
- [x] Added/updated automated tests
- [x] QA'd all new/changed functionality manually
Fixing https://github.com/fleetdm/fleet/actions/runs/18150944735.
- It seems that when not using the RC versions it cannot determine the
version of the github.com/fleetdm/fleet/v4 package , so it assumes it's
using `v4.0.0` thus causing alerts around our recent SAML vulnerability
(already fixed). So I'm changing it to only run on RC cuts, not every
day.
- Also adding a skip rule for a new CVE that we are not affected by.
Closes: #33723
Changes:
- Removed the segment analytics tag and all related code.
- Removed the `analytics` global from the .eslintrc in the
website/assets/ folder
On the pricing page (https://fleetdm.com/pricing) there are currently
two buttons that say Get a demo — one in the header and one on the
pricing table. Could we explore changing the button in the table to say
Talk to sales,Get a quote, or something similar and change the backend
routing to go directly to a sales queue to pick up? The thinking: if a
buyer is already going to that page, they likely want to talk to sales
to get a quote. They also have an opportunity to still book a demo on
that page in the header.
Closes https://github.com/fleetdm/confidential/issues/12102
