Description

I've tested with aap-dev now and confirmed POST /api/gateway/v1/role_user_assignments/ yielding

    "created": "2025-08-08T19:46:52.486501Z",

will correspondingly yield this at /api/controller/v2/role_user_assignments/

            "created": "2025-08-08T19:46:52.486501Z",

And they match!

Updated:

Added object_created to the /service-index/ serializer for role assignments, which can be used to validate that the object is the originally-assigned object as an additional check.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test update
• Refactoring (no functional changes)
• Development environment change
• Configuration change

Self-Review Checklist

• I have performed a self-review of my code
• I have added relevant comments to complex code sections
• I have updated documentation where needed
• I have considered the security impact of these changes
• I have considered performance implications
• I have thought about error handling and edge cases
• I have tested the changes in my local environment

Testing Instructions

Give permission to object in controller using Gateway API

compare & contrast the serializers

Prerequisites

Steps to Test

Expected Results

Additional Context

Required Actions

• Requires documentation updates
• Requires downstream repository changes
• Requires infrastructure/deployment changes
• Requires coordination with other teams
• Blocked by PR/MR: #XXX

Screenshots/Logs