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

SONiC YANG model support for RADIUS. #13760

Merged
merged 2 commits into from
Feb 10, 2023
Merged

SONiC YANG model support for RADIUS. #13760

merged 2 commits into from
Feb 10, 2023

Conversation

shdasari
Copy link
Contributor

Why I did it

Added SONiC YANG model for RADIUS.

How I did it

Added the RADIUS and RADIUS_SERVER tables for global and per RADIUS server configuration. RADIUS statistics reside in COUNTERS_DB and are not part of the configuration. These are not a part of this PR.

How to verify it

Compiled sonic_yang_mgmt-1.0-py3-none-any.whl.

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

Description for the changelog

SONiC YANG model for RADIUS.

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@xumia
Copy link
Collaborator

xumia commented Feb 10, 2023

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yxieca
Copy link
Contributor

yxieca commented Feb 10, 2023

@shdasari in future, when you help cherry-picking a change from master branch, please mention the original PR in the PR comments. So that I can mark the original PR as cherry-picked.

I suppose you are cherry-picking #12749?

@yxieca yxieca merged commit 0af9feb into sonic-net:202205 Feb 10, 2023
@shdasari
Copy link
Contributor Author

@shdasari in future, when you help cherry-picking a change from master branch, please mention the original PR in the PR comments. So that I can mark the original PR as cherry-picked.

I suppose you are cherry-picking #12749?

Yes, I have cherry-picked #12749. Will add original PR number henceforth.

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.

3 participants