fix(coral): Make all env available when using prefix in ACL request (#…

…1145)

when choosing the PREFIXED pattern type in environment Select input in ACL forms, all environments would be disabled and render a wrong state, because the prefix may not be === an existing topic name.

In regards to how the PREFIXED option is used, we should allow all environments to be chosen in this case.

Signed-off-by: Mathieu Anderson <mathieu.anderson@aiven.io>

coral/src/app/features/topics/acl-request/fields/EnvironmentField.tsx

@@ -5,13 +5,23 @@ import { ExtendedEnvironment } from "src/app/features/topics/acl-request/queries
 interface EnvironmentFieldProps {
   environments: ExtendedEnvironment[];
   selectedTopic?: string;
+  prefixed?: boolean;
 }
 
 const getOptions = (
   environments: ExtendedEnvironment[],
+  prefixed: boolean,
   topicName?: string
 ) => {
   return environments.map((env) => {
+    if (prefixed) {
+      return (
+        <Option key={env.id} value={env.id}>
+          {env.name}
+        </Option>
+      );
+    }
+
     if (env.topicNames.length === 0) {
       return (
         <Option key={env.id} value={env.id} disabled>
@@ -39,6 +49,7 @@ const getOptions = (
 const EnvironmentField = ({
   environments,
   selectedTopic,
+  prefixed = false,
 }: EnvironmentFieldProps) => {
   return (
     <NativeSelect
@@ -47,7 +58,7 @@ const EnvironmentField = ({
       placeholder={"-- Please select --"}
       required
     >
-      {getOptions(environments, selectedTopic)}
+      {getOptions(environments, prefixed, selectedTopic)}
     </NativeSelect>
   );
 };

coral/src/app/features/topics/acl-request/forms/TopicProducerForm.tsx

@@ -141,6 +141,7 @@ const TopicProducerForm = ({
             <EnvironmentField
               environments={environments}
               selectedTopic={topicname}
+              prefixed={aclPatternType === "PREFIXED"}
             />
           </GridItem>