Hello,
While reviewing the role import_workloads (specifically roles/import_workloads/tasks/create_network_port.yml), we noticed that Security Groups are always passed to the create_network_port module:
security_groups: ["{{ security_groups | default('default') }}"]
This enforces Security Group assignment (defaulting to default) during port creation.
In some environments, Security Groups are either not used or are managed externally, and we need the ability to create ports without attaching any Security Groups.
Could you please consider adding an option (e.g., a boolean variable such as use_security_groups: false) that would:
Skip setting the security_groups parameter entirely
Avoid defaulting to default when not explicitly defined
This would improve flexibility and compatibility with restricted or externally managed networking environments.
Or the possibility of creating ports without an associated Security Group, with the option --disable-port-security or something like that.
Thank you in advance
Hello,
While reviewing the role import_workloads (specifically roles/import_workloads/tasks/create_network_port.yml), we noticed that Security Groups are always passed to the create_network_port module:
security_groups: ["{{ security_groups | default('default') }}"]
This enforces Security Group assignment (defaulting to default) during port creation.
In some environments, Security Groups are either not used or are managed externally, and we need the ability to create ports without attaching any Security Groups.
Could you please consider adding an option (e.g., a boolean variable such as use_security_groups: false) that would:
Skip setting the security_groups parameter entirely
Avoid defaulting to default when not explicitly defined
This would improve flexibility and compatibility with restricted or externally managed networking environments.
Or the possibility of creating ports without an associated Security Group, with the option --disable-port-security or something like that.
Thank you in advance