Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] Add nodePort and loadbalancerIPAddress as optional fields in WG gateway template #2799

Merged

Conversation

claudiolor
Copy link
Contributor

Description

This PR introduces two features:

  • Templates can now have optional fields, which are identified by a ? (question mark) at the beginning of their name: : when a field in a template starts with the question mark and the value contains a variable, that field is rendered in the templateonly if that variable has a value.
  • nodePort and loadbalancerIPAddress are now present by default in the WG gateway server template, allowing the user to specify them without the need to manually add them in the template.

How Has This Been Tested?

Test suite has been provided

@adamjensenbot
Copy link
Collaborator

Hi @claudiolor. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

  • /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
    when the rebase operation is completed)
  • /merge: Merge this PR into the master branch
  • /build Build Liqo components
  • /test Launch the E2E and Unit tests
  • /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

  • kind/breaking: 💥 Breaking Change
  • kind/feature: 🚀 New Feature
  • kind/bug: 🐛 Bug Fix
  • kind/cleanup: 🧹 Code Refactoring
  • kind/docs: 📝 Documentation

@claudiolor claudiolor changed the title [Feat] Add nodePort and loadbalancerIPAddress as optional fields in WG gateway [Feat] Add nodePort and loadbalancerIPAddress as optional fields in WG gateway template Oct 31, 2024
@claudiolor
Copy link
Contributor Author

/build

@claudiolor claudiolor added the kind/feature New feature or request label Oct 31, 2024
@claudiolor claudiolor marked this pull request as ready for review October 31, 2024 15:51
@claudiolor claudiolor force-pushed the clo/template-optional-values branch 2 times, most recently from 0ab99ed to 342818d Compare November 4, 2024 11:30
@fra98
Copy link
Member

fra98 commented Nov 19, 2024

/rebase test=true

This patch introduces a new syntax for the templates allowing the usage
of optional values: when a field in a template starts with ? (question
mark) and it contains a variable, that field is rendered in the template
only if that variable has a value.
This patch adds nodePort and loadbalancerIPAddress as optional fields
in the template of the Wireguard gateway server service. This allows to
specify those fields in the GatewayServer configuration without asking
the user to manually edit the template.
@fra98
Copy link
Member

fra98 commented Nov 19, 2024

/merge

@adamjensenbot adamjensenbot added the merge-requested Request bot merging (automatically managed) label Nov 19, 2024
@adamjensenbot adamjensenbot merged commit 1c112cb into liqotech:master Nov 19, 2024
13 checks passed
@adamjensenbot adamjensenbot removed the merge-requested Request bot merging (automatically managed) label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants