You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to be able to enable/disable not the whole firewall, as I can do now, but just a specific enable/disable rule, that is already existing and preconfigured.
Describe the solution you'd like upctl server modify $SERVER_ID --enable-firewall-rule=10
Describe alternatives you've considered
Currently I have to disable the whole firewall to make an automation that requires 80 port wide opened.
Additional context
Required for let's encrypt work.
The text was updated successfully, but these errors were encountered:
Unfortunately, our API does not currently support enabling or disabling individual firewall rules. The best alternative at the moment would be to remove that specific rule with upctl server firewall delete and later re-create it with upctl server firewall create.
Hello @kangasta ! Yeah, I'm aware of that, thank you! I just believe that it would make sense to have that. Probably, altogether with a separate ACL that enables me to only let my service account to deal with firewall of the server, but not with the server itself - that permission feels quite vague (and not quite secure).
Is your feature request related to a problem? Please describe.
I would like to be able to enable/disable not the whole firewall, as I can do now, but just a specific enable/disable rule, that is already existing and preconfigured.
Describe the solution you'd like
upctl server modify $SERVER_ID --enable-firewall-rule=10
Describe alternatives you've considered
Currently I have to disable the whole firewall to make an automation that requires 80 port wide opened.
Additional context
Required for let's encrypt work.
The text was updated successfully, but these errors were encountered: