Bug 48269 – How to handle default values of udm object properties

Bug 48269 - How to handle default values of udm object properties


Summary:	How to handle default values of udm object properties

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-12-05 12:10 CET by Ole Schwiegert
Modified:	2021-05-14 16:34 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ole Schwiegert

2018-12-05 12:10:50 CET

Using the simple UDM API we have access to udm object properties via

obj.props.property_name

I got myself a user object that way which had an empty displayName property. It defaults to <firstname> <lastname>

In the simple UDM API the value when accessing user.props.displayName was None.

This mirrors the behavior of the old_udm_obj.get('displayName')

Here it differs from old_udm_obj['displayName'] which would return an empty string (or empty list for multivalue) or the specified default if a flag was set to true beforehand.

I think we need to consider this behavior of the original UDM Api and evaluate the current behavior of simple UDM API.

Comment 1 Ingo Steuwer

2021-05-14 15:42:36 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.