This pull request introduces new configuration profiles to support Okta conditional access for macOS devices, specifically targeting the Information Technology department. It also updates the GitHub Actions workflow to include a new secret for the Okta CA certificate. Additionally, it removes the `workstations-canary` team configuration, likely as part of a cleanup or migration. The most important changes are: **Conditional Access and Okta Integration:** * Added a new configuration profile, `fleet-okta-conditional-access.mobileconfig`, to manage trusted CA certificates, SCEP enrollment, mTLS identity preferences, and Chrome mTLS auto-selection for Okta conditional access on macOS. This profile is applied to devices labeled with "Department: Information Technology". [[1]](diffhunk://#diff-904aba5588b0d2c8dc325414aa1e8f2cd8a324602ac8e0c1cd2a5dff28db357bR1-R157) [[2]](diffhunk://#diff-96f80858f5a487334ae6014cddaa65d1bb79d7e85fa0ea596d1e49063f5b99bdR72-R77) * Added a new configuration profile, `okta-verify-settings.mobileconfig`, to configure privacy preferences, managed login items, notification settings, and Okta Verify app settings for macOS devices in the Information Technology department. [[1]](diffhunk://#diff-b321656e070ad9cb0727fe7ced60565d88bf31d236ac2642d3192fcb375fa4b2R1-R129) [[2]](diffhunk://#diff-96f80858f5a487334ae6014cddaa65d1bb79d7e85fa0ea596d1e49063f5b99bdR72-R77) **Workflow and Secrets Management:** * Updated the GitHub Actions workflow (`dogfood-gitops.yml`) to include the `DOGFOOD_OKTA_CA_CERTIFICATE` secret, supporting the new Okta conditional access configuration. **Configuration Cleanup:** * Removed the `workstations-canary.yml` team configuration, eliminating its policies, software, scripts, and settings. --------- Co-authored-by: Allen Houchins <32207388+allenhouchins@users.noreply.github.com> Co-authored-by: Allen Houchins <allenhouchins@mac.com> |
||
|---|---|---|
| .. | ||
| config | ||
| build-binaries.yaml | ||
| build-fleetd-base-msi.yml | ||
| build-fleetd-base-pkg.yml | ||
| build-fleetd_tables.yaml | ||
| build-fleetdm-fleetctl-check-vulnerabilities.yml | ||
| build-orbit.yaml | ||
| check-automated-doc.yml | ||
| check-bomutils-vulnerabilities.yml | ||
| check-ms-protocol-feeds.yml | ||
| check-script-diff.yml | ||
| check-tuf-timestamps.yml | ||
| check-updates-timestamps.yml | ||
| check-vulnerabilities-in-released-docker-images.yml | ||
| check-wix-vulnerabilities.yml | ||
| close-stale-eng-initiated-issues.yml | ||
| code-sign-windows.yml | ||
| codeql-analysis.yml | ||
| collect-eng-metrics-test.yml | ||
| collect-eng-metrics.yml | ||
| db-upgrade-test.yml | ||
| dependency-review.yml | ||
| deploy-fleet-website.yml | ||
| deploy-vulnerability-dashboard.yml | ||
| docs.yml | ||
| dogfood-automated-policy-updates.yml | ||
| dogfood-deploy.yml | ||
| dogfood-gitops.yml | ||
| dogfood-signoz-deploy.yml | ||
| dogfood-update-testing-qa-apps.yml | ||
| fleet-and-orbit.yml | ||
| fleetctl-preview-latest.yml | ||
| fleetctl-preview.yml | ||
| fleetd-tuf.yml | ||
| generate-desktop-targets.yml | ||
| generate-nudge-targets.yml | ||
| generate-osqueryd-targets.yml | ||
| generate-swift-dialog-targets.yml | ||
| golangci-lint.yml | ||
| goreleaser-fleet.yaml | ||
| goreleaser-orbit.yaml | ||
| goreleaser-snapshot-fleet.yaml | ||
| ingest-maintained-apps.yml | ||
| integration.yml | ||
| loadtest-infra.yml | ||
| loadtest-osquery-perf.yml | ||
| loadtest-shared.yml | ||
| pr-helm.yaml | ||
| publish-go-module.yml | ||
| randokiller-go.yml | ||
| README.md | ||
| release-fleetctl-docker-deps.yaml | ||
| release-fleetd-base.yml | ||
| release-fleetd-chrome-beta.yml | ||
| release-fleetd-chrome.yml | ||
| release-helm.yaml | ||
| render-deploy.yml | ||
| scorecards-analysis.yml | ||
| secrets-to-confidential.yml | ||
| test-android.yml | ||
| test-bulk-operations-dashboard-changes.yml | ||
| test-db-changes.yml | ||
| test-fleetd-chrome.yml | ||
| test-fma-darwin-pr-only.yml | ||
| test-fma-darwin.yml | ||
| test-fma-windows-pr-only.yml | ||
| test-fma-windows.yml | ||
| test-go.yaml | ||
| test-js.yml | ||
| test-mock-changes.yml | ||
| test-native-tooling-packaging.yml | ||
| test-packaging-build-docker-deps.yml | ||
| test-packaging.yml | ||
| test-puppet.yml | ||
| test-vulnerability-dashboard-changes.yml | ||
| test-website.yml | ||
| test-yml-specs.yml | ||
| tfvalidate.yml | ||
| trivy-scan.yml | ||
| update-certs.yml | ||
| update-old-tuf-timestamp-signature.yaml | ||
| update-osquery-versions.yml | ||
| validate-maintained-apps-inputs.yml | ||
| verify-fleetd-base.yml | ||
Github Actions
Fleet uses Github Actions for continuous integration (CI). This document describes best practices and at patterns for writing and maintaining Fleet's Github Actions workflows.
Bash
By default, Github Actions sets the shell to bash -e for linux and MacOS runners. To help write
safer bash scripts in run jobs and avoid common issues, override the default by adding the following
to the workflow file
defaults:
run:
# fail-fast using bash -eo pipefail. See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference
shell: bash
By specifying the default shell to bash, some extra flags are set. The option pipefail changes
the behaviour when using the pipe | operator such that if any command in a pipeline fails, that
commands return code will be used a the return code for the whole pipeline. Consider the following
example in test-go.yaml
- name: Run Go Tests
run: |
# omitted ...
make test-go 2>&1 | tee /tmp/gotest.log
If the pipefail option was not set, this job would always succeed because tee would always
return success. This is not the intended behavior. Instead, we want the job to fail if make test-go fails.
Concurrency
Github Action runners are limited. If a lot of workflows are queued, they will wait in pending until a runner becomes available. This has caused issue in the past where workflows take an excessively long time to start. To help with this issue, use the following in workflows
# This allows a subsequently queued workflow run to interrupt previous runs
concurrency:
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id}}
cancel-in-progress: true
When a workflow is triggered via a pull request, it will cancel previous running workflows for that
pull request. This is especially useful when changes are pushed to a pull request frequently.
Manually triggered workflows, workflows that run on a schedule, and workflows triggered by pushes to
main are unaffected.