Skip to content

fix: resolve additional LANs when primary LAN set via lan-id#141

Open
rmocanu-ionos wants to merge 1 commit into
masterfrom
fix/additional-lans-ignored
Open

fix: resolve additional LANs when primary LAN set via lan-id#141
rmocanu-ionos wants to merge 1 commit into
masterfrom
fix/additional-lans-ignored

Conversation

@rmocanu-ionos
Copy link
Copy Markdown
Contributor

Additional-LAN name-to-ID resolution previously ran only when no primary LAN id was configured, so --ionoscloud-additional-lans was silently ignored whenever the primary NIC was selected via --ionoscloud-lan-id. Run the resolution regardless of how the primary LAN is chosen.

Also add --ionoscloud-additional-lans-ids to attach LANs by numeric id, merged and de-duplicated with ids resolved from names.

What does this fix or implement?

fixes #140

Checklist

  • PR name added as appropriate (e.g. feat:/fix:/doc:/test:/refactor:)
  • Tests added or updated
  • Documentation updated
  • Sonar Cloud Scan
  • Changelog updated and version incremented (label: upcoming release)
  • Github Issue linked if any
  • Jira task updated

Additional-LAN name-to-ID resolution previously ran only when no primary
LAN id was configured, so --ionoscloud-additional-lans was silently
ignored whenever the primary NIC was selected via --ionoscloud-lan-id.
Run the resolution regardless of how the primary LAN is chosen.

Also add --ionoscloud-additional-lans-ids to attach LANs by numeric id,
merged and de-duplicated with ids resolved from names.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.

additionalLans are ignored when primary LAN is configured via lanId

2 participants