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

Seport local #1

Open
wants to merge 1 commit into
base: seport_local
Choose a base branch
from
Open

Conversation

richm
Copy link

@richm richm commented Sep 6, 2022

No description provided.

@bachradsusi
Copy link
Owner

What s your plan with this? seport_local was just a WIP branch with POC. I didn't plan to use it for anything else.

@richm
Copy link
Author

richm commented Sep 6, 2022

What s your plan with this? seport_local was just a WIP branch with POC. I didn't plan to use it for anything else.

I think linux-system-roles#123 should replace linux-system-roles#122, and this PR is an addition to your linux-system-roles#123

@bachradsusi
Copy link
Owner

I see. Using this PR in the other PR seems to unnecessary complicates things. I don't really insist on my commit in linux-system-roles#123 especially when it needs to be fixed. It was just a proof of concept.

Feel free to take seport from collections and do all necessary changes in your branch and PR.

@richm richm force-pushed the seport_local branch 3 times, most recently from 9faa76e to 1e7aeed Compare September 13, 2022 17:56
@richm richm force-pushed the seport_local branch 2 times, most recently from 0240336 to ca9dabd Compare September 15, 2022 00:53
`community.general.seport` has recently added the `local` parameter
which is now supported by the role.

- `local: true`:
  * `state: present` enforces change to be made even though the
    port mapping could already exists in built in policy
  * `state: absent` would remove only local modification and would not
    try to remove builtin mapping.

The role vendors-in the seport module as `local_seport`, because otherwise
it is too difficult to support both Ansible 2.9 and ansible-core.  We will
revisit this when Ansible 2.9 is EOL.
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.

2 participants