Ignore unknown properties on endpoints in endpoint rules.

[alextwoods]

Warn instead of raising an exception on unknown endpoint properties.

Motivation and Context

The Rules engine Endpoint Object Properties member is defined as an arbitrary Map<string, object> and to support forwards compatibility/extensibility and comply with the specification, we should not be failing when an unknown property is present in the rules.

Modifications

• Change the exception to a logger warning when an unknown (at this point, anything other than authSchemes) property is encountered in an Endpoint object.

Testing

Added new test case with endpoint rules with unknown property.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.