Skip to content

RDKCOM-5575: RDKBDEV-3419 ,RDKBACCL-1597: [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias#199

Open
SsandhyaR wants to merge 3 commits into
rdkcentral:mainfrom
SsandhyaR:1571-Alias
Open

RDKCOM-5575: RDKBDEV-3419 ,RDKBACCL-1597: [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias#199
SsandhyaR wants to merge 3 commits into
rdkcentral:mainfrom
SsandhyaR:1571-Alias

Conversation

@SsandhyaR

Copy link
Copy Markdown

Reason for change: Added SetHandler for Alias data model
Test procedure: set operation for not valid datatype should fail for Device.X_RDK_WanManager.Interface..Alias
Risks: Low

…Device.X_RDK_WanManager.Interface.<i>.Alias

Reason for change: Added SetHandler for Alias data model
Test procedure: set operation for not valid datatype should fail for Device.X_RDK_WanManager.Interface.<i>.Alias
Risks: Low

Signed-off-by: ssiras826 <ssiras826@cable.comcast.com>
@SsandhyaR SsandhyaR requested a review from a team as a code owner April 8, 2026 10:44
@SsandhyaR SsandhyaR marked this pull request as draft April 8, 2026 10:45
@SsandhyaR SsandhyaR marked this pull request as ready for review April 13, 2026 12:31
@SsandhyaR SsandhyaR changed the title RDKBACCL-1597 : [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias RDKBDEV-3419 ,RDKBACCL-1597 : [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias Apr 13, 2026
@AkhilaReddyK7

Copy link
Copy Markdown

PR is tracked at https://ccp.sys.comcast.net/browse/RDKCOM-5575

@pradeeptakdas pradeeptakdas changed the title RDKBDEV-3419 ,RDKBACCL-1597 : [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias RDKCOM-5576: RDKBDEV-3419 ,RDKBACCL-1597: [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias Apr 14, 2026
@pradeeptakdas pradeeptakdas changed the title RDKCOM-5576: RDKBDEV-3419 ,RDKBACCL-1597: [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias RDKCOM-5575: RDKBDEV-3419 ,RDKBACCL-1597: [TDK][AUTO][BPI][DML]Write-Type compliance fails for Device.X_RDK_WanManager.Interface.<i>.Alias Apr 14, 2026
CcspTraceInfo(("%s-%d : Selection Enable UnSub(%d) \n", __FUNCTION__, __LINE__, pWanDmlIface->Sub.WanEnableSub));
}
}
else if(strstr(name, WANMGR_INFACE_ALIASNAME_SUFFIX))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is there a requirement to subscribe to the “Alias” event?

If so, I’d like to understand the details to ensure we are sending the events correctly.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Hi @guto86 ,
modified the code with removing event, please review

Copilot AI review requested due to automatic review settings June 9, 2026 13:18

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds RBUS set-handler support for updating a WAN interface’s AliasName and persisting it to PSM/DB.

Changes:

  • Handle ...AliasName parameter updates in WanMgr_Interface_SetHandler.
  • Copy the new alias into the in-memory interface object and persist it via WanMgr_RdkBus_SetParamValuesToDB.
  • Log alias changes for visibility.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +589 to +591
char param_name[256] = {0};
strncpy(AliasName, rbusValue_GetString(value, NULL), sizeof(AliasName)-1);
_ansc_sprintf(param_name, PSM_WANMANAGER_IF_ALIAS, index);
{
if (type == RBUS_STRING)
{
char AliasName[64] = {0};
char param_name[256] = {0};
strncpy(AliasName, rbusValue_GetString(value, NULL), sizeof(AliasName)-1);
_ansc_sprintf(param_name, PSM_WANMANAGER_IF_ALIAS, index);
strncpy(pWanDmlIface->AliasName, AliasName, sizeof(pWanDmlIface->AliasName)-1);
ret = RBUS_ERROR_INVALID_INPUT;
}
}
else if(strstr(name, WANMGR_INFACE_ALIASNAME_SUFFIX))
@guto86

guto86 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Hi @SsandhyaR,

While the implementation looks good overall, we would like you to consider the Pub/Sub behavior.
Specifically, if any component subscribes to a WanManager DML via an alias, it must be notified when that alias changes. The alias is used as an indexer for all queries and subscriptions across RDK DMLs, so consistency is critical.
Example:
Device.X_RDK_WanManager.Interface.[DOCSIS].Selection.Status

@SsandhyaR

Copy link
Copy Markdown
Author

Hi @SsandhyaR,

While the implementation looks good overall, we would like you to consider the Pub/Sub behavior. Specifically, if any component subscribes to a WanManager DML via an alias, it must be notified when that alias changes. The alias is used as an indexer for all queries and subscriptions across RDK DMLs, so consistency is critical. Example: Device.X_RDK_WanManager.Interface.[DOCSIS].Selection.Status

Hi @guto86 ,
will create a new ticket to track this enhancement. Meanwhile, is it possible to merge this change?

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.

4 participants