Module access_request_crd 

White-labeled naming for the access-request custom resource.

The operator manifest (alien-helm) and the operator runtime (alien-access-request-crd-loop) BOTH derive the CRD’s group/kind/plural from the deployment’s brand name here, so the resource the manifest registers is exactly the one the operator creates and watches — they can’t drift.

Kubernetes requires the API group to be shaped like a DNS subdomain, but never resolves it — so the brand isn’t a domain the vendor owns, just a stable, customer-facing identity (e.g. the project name) slugified into that shape.

For a vendor branded acme, the access-request CRD is:

group:  accessrequests.acme
kind:   AcmeAccessRequest
plural: acmeaccessrequests
short:  acmear

When no brand is set it falls back to the Alien defaults (accessrequests.alien / AlienAccessRequest).

Structs

AccessRequestCrdNames

Derived, white-labeled names for the access-request custom resource.

Constants

ACCESS_REQUEST_CRD_VERSION

The CRD version served (single alpha version for now).

DEFAULT_BRAND

The default (unbranded) slug the access-request CRD lives under.

Functions

access_request_crd_names

Derive the access-request-CRD names from a brand name (e.g. Some("acme"), or Some("Acme Corp")). None/empty → the Alien defaults.