Audit Log: Track RBAC changes

[AndrienkoAleksandr]

What does this pull request do

Implement audit logging for RBAC backend

Referenced issue:

https://issues.redhat.com/browse/RHIDP-2004

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from andrienkoaleksandr. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Audit Log: Track RBAC changes". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat
 - fix
 - chore
 - docs
 - style
 - refactor
 - perf
 - test
 - revert

[Zaperex]

Upstream backstage is moving towards using their LoggerService (also refer to the implementation) instead of the winston Logger. The LoggerService does not contain this log function so we should be using the info and error functions instead to make migration to LoggerService in the future easier.

To get the same behavior as using log, you'll need to put the non message fields in the metadata argument of the info or error function. Otherwise, the object containing your audit log message will be logged as an object in the message field. This would result in [object Object] being printed if the logger format isn't JSON.

[sonarcloud]

Please retry analysis of this Pull-Request directly on SonarCloud

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Zaperex]

Suggested change

	this.logger.info(
	`${this.fmtToPastTime(operation)} '${metadata.roleEntityRef}'`
	this.toLogMsgWithRoleInfo(logMsg, metadata)
	);
	this.logger.info(
	`${this.fmtToPastTime(operation)} '${metadata.roleEntityRef}'`,
	this.toLogMsgWithRoleInfo(logMsg, metadata)
	);

[sonarcloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[AndrienkoAleksandr]

close on favour: #1694