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

feature/default-switch-packetfence-standard #5742

Merged
merged 3 commits into from
Sep 16, 2020

Conversation

jrouzierinverse
Copy link
Member

@jrouzierinverse jrouzierinverse commented Aug 10, 2020

Description

Set the default switch type to Packetfence::Standard

NEWS file entries

Enhancements

  • Set the default switch type to Packetfence::Standard
  • Create a PacketFence::SNMP switch to force reevaluate access using SNMP

Issue

fixes #5490

Delete branch after merge

NO

UPGRADE file entries

Set the switch type to Generic if it was not previously defined.

/usr/local/pf/addons/upgrade/to-10.2-default-switch-packetfence-standard.pl

Checklist

  • Document the feature
  • Add unit tests
  • Add acceptance tests (TestLink)

Copy link
Contributor

@nqb nqb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an ambiguity for addons/upgrade/to-10.2-default-switch-packetfence-standard.pl script.

Name of script doesn't match its description: "Rename Generic switch type to Packetfence::SNMP" and its actions: script is trying to set Generic value for switches.

@jrouzierinverse jrouzierinverse force-pushed the feature/default-switch-packetfence-standard branch from ba3a679 to 1618a5d Compare August 11, 2020 20:03
@jrouzierinverse
Copy link
Member Author

Fixed the verbage

@jrouzierinverse jrouzierinverse force-pushed the feature/default-switch-packetfence-standard branch from 67ae9e6 to 1618a5d Compare September 10, 2020 18:15
Copy link
Contributor

@nqb nqb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not remove Generic switch module too ?

Copy link
Contributor

@nqb nqb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to replace Generic switch module by PacketFence::Standard switch module, we should first merge #5708, rebase and add cliAuthorizeRead and cliAuthorizeWrite scopes to PacketFence::Standard switch module based on what we do in Generic switch module.

I can take care of this change.

@jrouzierinverse
Copy link
Member Author

Let's remove the Generic switch in 11.0.

@jrouzierinverse
Copy link
Member Author

There is no need to add cliAuthorizeRead and cliAuthorizeWrite scopes to PacketFence::Standard.
As it has the same behavior of the Generic module if none are defined.

@nqb nqb merged commit 2dc4688 into devel Sep 16, 2020
nqb added a commit that referenced this pull request Sep 16, 2020
satkunas pushed a commit that referenced this pull request Dec 11, 2020
@satkunas satkunas deleted the feature/default-switch-packetfence-standard branch May 15, 2024 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RFC: use "PacketFence::Standard" in place of "Generic" for default Switch Group
2 participants