Add integrator and child account support #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1️⃣ This PR introduces full support for PrintNode Integrator accounts, fulfilling a direct user request for managing child accounts.
2️⃣ All changes are cohesive and directly related to the implementation of Integrator account functionality.
3️⃣ Yes, comprehensive unit and feature tests have been added for the
AccountService,Accountentity, andAccountRequestbuilder.4️⃣ This improvement adds robust support for PrintNode Integrator accounts, enabling developers to programmatically manage child accounts. This is crucial for multi-tenant applications (e.g., SaaS platforms) that need to provide isolated printing capabilities to their customers.
Key features include:
X-Child-Account-By-IdorX-Child-Account-By-CreatorRefheaders.This functionality allows for a more secure, scalable, and automated way to integrate PrintNode into complex applications, centralizing control while maintaining customer data separation. Extensive documentation has also been added to guide usage.
5️⃣ Thanks for contributing! 🙌