Skip to content

refactor(firewall): rename to Security Group - #8

Draft
r-gues wants to merge 1 commit into
super-phenix:mainfrom
r-gues:rename-firewall
Draft

refactor(firewall): rename to Security Group#8
r-gues wants to merge 1 commit into
super-phenix:mainfrom
r-gues:rename-firewall

Conversation

@r-gues

@r-gues r-gues commented Jul 30, 2026

Copy link
Copy Markdown
Member

No description provided.

@r-gues r-gues self-assigned this Jul 30, 2026
Match the backend rename shipped in superphenix 2ca0031.

Wire contract:
- endpoint /firewall -> /security-group
- response wrapper field firewall -> securityGroup
- product type discriminator firewall -> securityGroup
- ProjectFirewallRead/Write -> ProjectSecurityGroupRead/Write

Request bodies are structurally unchanged: general/spec, target, ingress,
egress, ports, from, to, allowAll, denyAll, matchLabels, matchExpressions,
podSelector and IPBlock/CIDR/Except keep their JSON names.

Code and user-facing labels renamed throughout: 05_firewall ->
05_security_group, models/network/firewall -> models/network/security-group,
FirewallService -> SecurityGroupService, Firewall* -> SecurityGroup*
components and spx-security-group-* selectors. All visible strings now read
"Security Group".

Backwards compatibility for URLs predating the rename:
- a legacy 'firewall' route redirects to 'security-group', preserving child
  segments and :az/:id params (covered by network.routes.spec.ts)
- ProductTypeLink keeps a 'firewall' alias so previously shared
  /redirect/.../firewall/<id> links still resolve; that entry point goes
  through getProduct(), which a router redirect cannot cover

localStorage keys become security_group_show_cluster / security_group_refresh
with no migration: they are UI toggles, so users get defaults once.

KaaS keeps the /netpols endpoint path and its "Network Policies" wording (the
Kubernetes concept), but is now gated by ProjectSecurityGroupRead.

Behaviour change beyond the rename: the route guard checked
ProjectLoadBalancerRead due to a copy-paste bug and now checks
ProjectSecurityGroupRead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant