| name | contentstack-management |
|---|---|
| description | Public CMA surface—Client, Stack, _APIClient, domain resources, OAuth; align with CMA docs and semver. |
- Implementing or changing
Client, Stack, or resource modules (entries, assets, webhooks, …). - Updating
README.mdor public exports for user-visible behavior. - Assessing semver impact of constructor, method, or export changes.
contentstack_management.Clientincontentstack.py: builds CMA endpoint from region / host / scheme, merges headers (authtoken, management_token, early_access), constructs_APIClient, optionaloauth_configwithOAuthHandler.
Stack—contentstack_management/stack/stack.py: stack-scoped resources (content types, entries, assets, branches, webhooks, …).- Org / user —
organizations/,users/,user_session/as applicable. - Resources — packages under
contentstack_management/following existing patterns. - OAuth —
oauth/oauth_handler.py,oauth/oauth_interceptor.py; keep aligned with_APIClientrequest path.
_APIClient._call_request— central place for method, URL, JSON, files; respect timeout and max_retries.
- Add methods on the appropriate resource class; align path and payload shapes with CMA docs.
- Prefer routing HTTP through
_APIClientfor consistent retries and OAuth handling.
- Exported
Client,Region, and stack helpers should match README andcontentstack_management.__init__.py. - Document migration for intentional breaking changes.
- Content Management API
skills/framework/SKILL.mdskills/python-style/SKILL.md