You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While 2U's deployment will have a separate cluster per environment, that won't be true for all deployers, and it's still worth having a reminder of which environment you're in. So, while an IDA may be configured to produce or consume on topic cert-changed, we'll want the actual Kafka topic to be prod-cert-changed or similar.
A/C:
IDAs that use the event bus still just know about the "base" topic (no change)
event-bus-kafka reads optional Django setting EVENT_BUS_TOPIC_PREFIX containing a string like "prod" or "staging" that names an environment.
If the setting is present, the actual topic used will be f"{prefix}-{base_topic}"; if absent then just base_topic.
The text was updated successfully, but these errors were encountered:
While 2U's deployment will have a separate cluster per environment, that won't be true for all deployers, and it's still worth having a reminder of which environment you're in. So, while an IDA may be configured to produce or consume on topic
cert-changed
, we'll want the actual Kafka topic to beprod-cert-changed
or similar.A/C:
EVENT_BUS_TOPIC_PREFIX
containing a string like"prod"
or"staging"
that names an environment.f"{prefix}-{base_topic}"
; if absent then justbase_topic
.The text was updated successfully, but these errors were encountered: