HYPERFLEET-1237 - feat: add authorization header support for api_call

.pre-commit-config.yaml

@@ -19,7 +19,7 @@ repos:
 
   # File hygiene
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v6.0.0 # v6.0.0
+    rev: 3e8a8703264a2f4a69428a0aa4dcb512790b2c8c # v6.0.0
     hooks:
       - id: trailing-whitespace
       - id: end-of-file-fixer

Dockerfile

@@ -1,6 +1,6 @@
 ARG BASE_IMAGE=registry.access.redhat.com/ubi9-micro:latest
 
-FROM registry.access.redhat.com/ubi9/go-toolset:9.8-1781757851 AS builder
+FROM registry.access.redhat.com/ubi9/go-toolset:9.8-1779959429 AS builder
 
 ARG GIT_SHA=unknown
 ARG GIT_DIRTY=""

README.md

@@ -28,13 +28,13 @@ The adapter requires a running message broker and HyperFleet API. The [hyperflee
 |---------|-----------------|
 | `make local-up-gcp` | GKE cluster + images + API + adapters + Maestro |
 | `make install-hyperfleet` | Everything on an existing K8s cluster using RabbitMQ (no GCP needed) |
-| `make install-adapters` | Install sample Hyperfleet Adapters |
+| `make install-hyperfleet-adapters` | Install sample Hyperfleet Adapters |
 | `make status` | Verify the deployment |
 
 Make sure you define the following environment variables:
 * `HELMFILE_ENV`: accepted values : `kind`, `gcp`
 * `NAMESPACE`: namespace where HyperFleet components will be deployed
-* `REGISTRY`: The registry namespace from which to pull the images. `quay.io/redhat-services-prod/hyperfleet-tenant/hyperfleet` for released images
+* `REGISTRY`: The registry namespace from which to pull the images. `quay.io/openshift-hyperfleet` for released images
 * `API_IMAGE_TAG`: image tag for `hyperfleet-api` container image
 * `SENTINEL_IMAGE_TAG`: image tag for `hyperfleet-sentinel` container image
 * `ADAPTER_IMAGE_TAG`: image tag for `hyperfleet-adapter` container image