-
Notifications
You must be signed in to change notification settings - Fork 43
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
Remove dependency on bash #79
Closed
Labels
good first issue
Good for newcomers
Comments
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
iptables-restore was being executed via bash, which was unnecessary. Executing directly is simpler and more reliable. Fixes: jodevsa#79
Bash is also used in two other places:
|
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
…t with native code There is no reason to use bash, or even to call out to the shell for most of what was happening. Replacing it allows for better error handling, clarity and reliability. Fixes: jodevsa#79
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
…t with native code There is no reason to use bash, or even to call out to the shell for most of what was happening. Replacing it allows for better error handling, clarity and reliability. Fixes: jodevsa#79
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
…t with native code There is no reason to use bash, or even to call out to the shell for most of what was happening. Replacing it allows for better error handling, clarity and reliability. Fixes: jodevsa#79
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
…t with native code There is no reason to use bash, or even to call out to the shell for most of what was happening. Replacing it allows for better error handling, clarity and reliability. Fixes: jodevsa#79
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
There is no reason to use bash, or even to call out to the shell for most of what was happening. Replacing it allows for better error handling, clarity and reliability. Fixes: jodevsa#79
jodevsa
pushed a commit
that referenced
this issue
May 9, 2024
iptables-restore was being executed via bash, which was unnecessary. Executing directly is simpler and more reliable. Fixes: #79
Closed
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 9, 2024
jodevsa
pushed a commit
that referenced
this issue
May 9, 2024
uhthomas
added a commit
to uhthomas/wireguard-operator
that referenced
this issue
May 10, 2024
There is no reason to use bash, or even to call out to the shell for most of what was happening. Replacing it allows for better error handling, clarity and reliability. Fixes: jodevsa#79
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are currently relying on bash in the agent to update the iptable rules. This isn't really needed and can be done without bash.
https://github.com/jodevsa/wireguard-operator/blob/main/internal/iptables/iptables.go#L27
The text was updated successfully, but these errors were encountered: