linode / linode/ansible_linode

[Feature]: append firewall rule on firewall

Open
#610 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
63
Forks
38
Avg merge
5d 20h
Merged PRs (30d)
7

Description

### Description

Running example playbook will result in firewall rule1 to dissapear from the firewall and rule2 to be the only one enforced.
I'm looking for a way to not be required to repeat the entire existing firewall config

### New/Affected Components

linode.cloud.firewall

### Example Ansible Config

```
- name: test linode firewall
gather_facts: false
hosts: localhost
tasks:
- name: Create a Linode Firewall1
linode.cloud.firewall:
label: "test_linode"
rules:
inbound:
- label: "test1"
addresses:
ipv4:
- "1.1.1.1/32"
description: "test1"
ports: 1
protocol: TCP
action: ACCEPT
outbound_policy: ACCEPT
inbound_policy: ACCEPT
state: present
- name: Create a Linode Firewall2
linode.cloud.firewall:
label: "test_linode"
rules:
inbound:
- label: "test2"
addresses:
ipv4:
- "2.2.2.2/32"
description: "test2"
ports: 2
protocol: TCP
action: ACCEPT
state: present
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied Ansible playbook and the linode.cloud.firewall component, reproducing the two tasks against the same firewall label. Trace how the second task handles the existing inbound rules and determine the expected append behavior. Done means the second task preserves rule1 while enforcing rule2, without requiring the full existing configuration to be repeated.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, python
Domain
cloud, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.