summaryrefslogtreecommitdiffstats
path: root/licenses/GitPython.txt (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-06-03Repin cython due to https://github.com/yaml/pyyaml/pull/702 (#15248)Hao Liu2-6/+12
* Revert "Unpin cypthon (#15246)" This reverts commit 659c3b64dec5fb8dd6eeabcb47e794cbbae9e8c4. * Pin grpcio Avoid cython 3 due to https://github.com/yaml/pyyaml/pull/702 * Delete asyncpg.txt
2024-06-03Unpin cypthon (#15246)Hao Liu3-215/+4
* Unpin cython * Remove unused asyncpg * Remove asyncpg license file
2024-06-02Add AWS SNS notification support for webhook (#15184)Ethem Cem Özkan21-21/+297
Support for AWS SNS notifications. SNS is a widespread service that is used to integrate with other AWS services(EG lambdas). This support would unlock use cases like triggering lambda functions, especially when AWX is deployed on EKS. Decisions: Data Structure - I preferred using the same structure as Webhook for message body data because it contains all job details. For now, I directly linked to Webhook to avoid duplication, but I am open to suggestions. AWS authentication - To support non-AWS native environments, I added configuration options for AWS secret key, ID, and session tokens. When entered, these values are supplied to the underlining boto3 SNS client. If not entered, it falls back to the default authentication chain to support the native AWS environment. Properly configured EKS pods are created with temporary credentials that the default authentication chain can pick automatically. --------- Signed-off-by: Ethem Cem Ozkan <ethemcem.ozkan@gmail.com>
2024-06-02Modify the link to terraform_state inventory plugin (#15241)Akira Yokochi2-3/+3
fix link to terraform_state inventory plugin
2024-05-31Add requirements commentChris Meyers1-1/+1
2024-05-31Add example grafana dashboardChris Meyers2-2/+160
* Per-service log view
2024-05-31Rework which loggers we sent to OTELChris Meyers1-4/+11
* Send all propagate=False loggers to OTEL AND the awx logger
2024-05-31Add recordingChris Meyers5-7/+45
* Always output awx logs to a file via otel * That log file can always be later replayed into a product that supports otlp at a later date. * Useful when you find a problem that you need a time series DB to help find and solve. * Useful if a community member or customer has a problem where a time series db would be helpful. You can take a "remote" users log and replay it locally for analysis.
2024-05-31Move requirements out of dev and into mainlineChris Meyers18-5/+2960
* Add new package license files
2024-05-31Centralized logging via otelChris Meyers11-0/+270