* WIP
* Add more logging
* Check rate limit at end of action
* Add github client in more places
* Add new published firefox 93 vulnerabilities to tests
* Remove fmt printfs
* Restore CI check settings
* Readd newline
* Initial work on customer terraform modules.
I'm getting lost so I'll need to start applying stuff to make sure it
works
* Stopping here for now
Next I need to add optional()'s to everything so we can specify partial
structure.https://developer.hashicorp.com/terraform/language/expressions/type-constraints#optional-object-type-attributes
* A random check in
Need to redo basically all variables and fix everything
* Got a lot more working finally!
* RDS and Elasticache now create
* Clean apply, just need debugging
* Should be fully working, just need to make a fully working example
* Everything is working and added a usage example
* Added contributing
* fixup
* Final wiring changes and ran the autodoc command
* Add more docs
* Fixup
* Add critical policies to pricing page
- Add "Mark issues as critical" for critical policies feature (Premium only)
- Feature will be included in the upcoming 4.25.0 release
- Move "Detect and surface issues with devices" above "Mark issues" as critical
* Update pricing-features-table.yml
* Add "(policies)"
Related to #8167, from RFC5280:
> The serial number MUST be a positive integer assigned by the CA to
> each certificate. It MUST be unique for each certificate issued by a
> given CA (i.e., the issuer name and serial number identify a unique
> certificate).
Without this change, we're issuing two different certificates with the
same serial number (1, one) and issuer name:
1. One during `fleetctl generate mdm-apple`
1. One during the first SCEP enrollment
* Make activities type and auto-generate docs for each type
* Add pageOrderInSection to not break site
* Add do not edit note to generated file
* Add make generate-doc step
* Fix main merge
A customer had a seccomp profile that seemed to be incompatible with the
changes in glibc in ubuntu-22.04. Setting the builder back to 20.04
explicitly to resolve this issue.
Reverse a previous change I made that was a mistake, and temporarily remove automated requests for review.
As it was, it wasn't working, and was just creating noise for more folks e.g. extra reviewers in https://github.com/fleetdm/fleet/pull/9001
* Improve how we are logging failed queries and windows detail queries
* Update failing tests
* Remove unneeded table in this particular select
* Update tests now that we dont rely on release_id
* Update ingestion since we want to ingest failures for policies and live queries
* We also want labels with failures
* Fix test since we are logging errors slightly differently
* Improve logging and error handling
* Revert back test change
* Actually, we need to OR the booleans to maintain logic