mirror of
https://github.com/fleetdm/fleet
synced 2026-05-17 22:18:39 +00:00
4 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Eric
|
2db26cd44e
|
Website: Add "Explore data" (#15400)
Closes: #14847 Changes: - Added two new pages: - `/try-fleet/explore-data`: A page where users can select a host, and be taken to a page where they can see query results for that host. - `try-fleet/explore-data/:platformName/:tableName`: A page where users can see the contents of osquery tables on hosts. - The view-action for this page will: - Redirect unauthenticated users to the /try-fleet/login page. (With a query parameter that will tell the login/register pages to redirect users back to this page) - Get information for hosts on a specified team. - Build a filtered list of osquery tables that are compatible with the host and have queries that will run on a specified host. - Get the latest query results for a specified query/osquery table for the specified host, and reorder the results to match the order of the columns in the osquery schema. - Updated build-static-content to add information about osquery tables for the /explore-data pages to `sails.config.builtStaticContent.osqueryTables`. - Added 5 new config variables: - `sails.config.custom.fleetBaseUrlForQueryReports`: The URL of the Fleet instance used for the /explore-data pages - `sails.config.custom.fleetTokenForQueryReports`: An API token for the Fleet instance used for the /explore-data pages - `sails.config.custom.teamApidForQueryReports`: the API ID of the team that the hosts listed on the explore-data page are in. - `sails.config.custom.queryIdsByTableName`: A dictionary containing key:value pairs where each key is the name of an osquery table, and the value is the API ID of the query that gets results for this table in a Fleet instance. This is stored in the custom configuration to make it easily editable (If we ever need to add or remove queries - `sails.config.custom.hostIdsByHostPlatform`: A dictionary containing key:value pairs where each key is a type of operating system, and the value is the API ID of a Host. - Updated the `/try-fleet` redirect to go to `/try-fleet/explore-data` - Updated the "try it out" button links to go to `/try-fleet` - Updated /try-fleet/login and /try-fleet/register to send users who are redirected to the page via the /explore-data page to the page they had tried to navigate to when they log in/create an account. I'm creating this as a PR as a draft. It will be ready to merge when we: - [x] Add hosts to the "Explore data (fleetdm.com) [DO NOT DELETE]" team - [x] Create queries for every compatible osquery table for the "Explore data (fleetdm.com) [DO NOT DELETE]" team. - [ ] Add a `sails.config.custom.queryIdsByTableName` config variable with the query IDs for the queries created in the previous step - [ ] Add `sails.config.custom.hostIdsByHostPlatform` config variable with the real host IDs/platforms |
||
|
Eric
|
4a6bf0d447
|
2023-10-24 Website: Update /try-fleet (#14638)
Closes: https://github.com/fleetdm/confidential/issues/4015 Changes: - Changed the url for `/fleetctl-preview` to `/try-fleet/fleetctl-preview` - Updated the controller for the `/fleetctl-preview` page to redirect non-logged-in users to `/try-fleet/login` - Removed the route for `/try-fleet/sandbox-expired`, and added a redirect going to `/try-fleet/fleetctl-preview`. - Updated the controller for `/try-fleet/sandbox` to redirect the users without a non-expired Sandbox instance to `/try-fleet/fleetctl-preview`. - Updated `signup.js` to not provision Fleet sandbox instances for users. - Updated the `User` model to support a third `signupReason`: "Try Fleet" - Updated `/try-fleet/register` to submit "Try Fleet" as a `signupReason` when users sign up. - Renamed the files for the `/fleetctl-preview` page (`get-started` » `fleetctl-preview`) - Updated/removed Fleet Sandbox related handbook sections. - Replaced the "Fleet vs Fleet Sandbox" section in the deploying documentation with a note about `fleetctl preview`. - Updated links to Fleet Sandbox in articles. --------- Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> |
||
|
Eric
|
47227d7bd3
|
Website: add Fleet Sandbox waitlist (#13028)
Changes: - Added a new config variable: `sails.config.custom.fleetSandboxWaitlistEnabled` - Added a new attribute to the website's `user` model: `inSandboxWaitlist` - Updated `signup.js` to create user accounts without a Fleet sandbox instance and `inSandboxWaitlist` set to true if `sails.config.custom.fleetSandboxWaitlistEnabled` is true. - Added /try-fleet/waitlist, a page that shows a message to users who have been added to the Fleet sandbox waitlist. - renamed`view-sandbox-teleporter-or-redirect-because-expired.js` to `view-sandbox-teleporter-or-redirect-because-expired-or-waitlist.js` and updated it to redirect users who are on the Fleet Sandbox waitlist to /try-fleet/waitlist Before this PR can be merged, we need to: - [x] Add `sails.config.custom.fleetSandboxWaitlistEnabled` config variable in Heroku. - [x] Add the new attribute to the user table in the website's database - [x] Update existing `user` records to have the new attribute (set to false) .. |
||
|
Eric
|
7974bdfa80
|
Website: Fleet Sandbox (#6380)
* create pages, add routes, update policies * add new pages to importer * sandbox page * login -> sandbox-login * Update login.less * psuedo-code/code comments * remove sandbox page * Revert "remove sandbox page" This reverts commit |