Rescope Idempotent Publishing for Internal Partner Integration

[jsquire]

Summary

In order to unblock releases of the Event Hubs client library packages, the preview API of the Idempotent Publishing feature was set to internal. Since that time, the decision was made to change the form which it will be exposed for general use. Because of existing commitments to an internal partner, the feature will need to be restored in a form suitable for public-but-not-public use.

The intention is to allow it to be used by determined parties that know it exists, but not have the feature appear in the public API listings or documentaiton. The pull requests in the "References and Related" section can be used as a reference for the changes made to internalize the feature.

Scope of Work

• Change the internal designation on the Idempotent Publishing types and members to a form where they can be used in the public scope but do not appear in listings or documentation as part of the public API surface.

• Review the approach used with the .NET architects.

• Create a prototype to illustrate to the interested parties how the changes can be used in their application.

Success Criteria

• The API surface needed to support the Idempotent Publishing feature is available in the public scope but does not appear as part of the public API listings or in documentation.

• The tests for the feature have been updated as needed and pass reliably.

• The existing test suite continues to produce deterministic results and pass reliably.

References and Related

• [Event Hubs Client] Internalize Idempotent Publishing (#18016)
• [Event Hubs Client] Minor Fixes (#18054)