List view
# Overview The **v0.6.0‑beta.1** milestone focuses on stabilising the core request pipeline, improving export functionality, and establishing consistent governance patterns across the module. This release aims to deliver a predictable, privacy‑first, and extensible foundation for further development. Key areas include: - CSV export for core Datto RMM objects - Consistent PII masking and reveal behaviour - Throttle and rate‑limit architecture review - Documentation and contributor‑experience improvements - Completion of the **Public Function Pipeline Parameter Cleanup** milestone (dependency) --- # Core Goals ### **1. Export Functionality** Introduce `Export-RMMObjectCsv` to provide a simple, opinionated CSV export for Sites, Devices, and Alerts. This includes flattened output, predictable column sets, and pipeline support. ### **2. Governance & Consistency** Standardise: - PII masking behaviour - usage of the existing DRMMObject masking helper - naming and behaviour of reveal parameters - contributor expectations for privacy‑sensitive fields ### **3. Request Pipeline Stability** Improve reliability and predictability of: - pagination - token refresh - error handling - verbose/debug tracing ### **4. Rate‑Limit & Throttle Architecture** A significant portion of this milestone depends on validating platform behaviour around: - legacy single‑bucket rate limits - sliding‑window write‑count decay - mixed read/write workflow performance These items are included in the milestone but currently **blocked** pending clarification or access to a suitable legacy environment. ### **5. Public Function Pipeline Parameter Cleanup (Dependency)** This milestone depends on the completion of the cross‑cutting cleanup work covering the following domains: - `Account` - `ActivityLog` - `Alerts` - `Auth` - `Component` - `Config` - `Devices` - `Filter` - `Jobs` - `Sites` - `Variables` This ensures consistent pipeline behaviour, predictable parameter naming, and backwards‑compatible aliasing across all public‑function domains. --- # Roadmap Notes (No Dates Committed) This milestone intentionally does **not** include delivery dates. Several tasks depend on external factors that cannot be reliably predicted, including: - validation of legacy `system/request_rate` behaviour - confirmation of write‑count decay correctness - access to a legacy‑mode tenant for testing - ability to run balanced read/write workflow tests once decay behaviour is stable Assigning dates would be speculative. Instead, the milestone focuses on defining the required work, documenting blockers clearly, and ensuring the architecture is ready to proceed as soon as the unknowns are resolved. --- # Dependencies This milestone **depends on the completion** of: - **Public Function Pipeline Parameter Cleanup** (milestone) All issues related to pipeline parameter standardisation, aliasing, and documentation live in that milestone. This milestone cannot be considered stable until the dependency milestone is complete. --- # Completion Criteria This milestone will be considered complete when: - CSV export is implemented and documented - PII masking behaviour is consistent across public functions - request pipeline stability improvements are merged - throttle and rate‑limit issues are either resolved or validated - the **Public Function Pipeline Parameter Cleanup** milestone is complete - all blocked items have clear next steps or confirmed dependencies
No due date•17/22 issues closed