Skip to content

fix: Added New Zscaler Cellular API endpoint resources and documentation, New ZPA and ZIA Endpoints#542

Merged
willguibr merged 8 commits into
masterfrom
zcell-#539-added-zcell-endpoint-resources
Jul 6, 2026
Merged

fix: Added New Zscaler Cellular API endpoint resources and documentation, New ZPA and ZIA Endpoints#542
willguibr merged 8 commits into
masterfrom
zcell-#539-added-zcell-endpoint-resources

Conversation

@willguibr

@willguibr willguibr commented Jul 6, 2026

Copy link
Copy Markdown
Member

Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.

Description

Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.

Has your change been tested?

Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.

Screenshots (if appropriate):

Types of changes

What sort of change does your code introduce/modify?

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • This change is using publicly documented and stable APIs.

willguibr added 7 commits July 1, 2026 12:02
Introduce a ZCell-specific  config attribute and
 environment variable that are automatically injected
into the  request path, so the customer id no longer has
to be passed on every ZCell call. Resolution precedence is explicit uid=501(wguilherme) gid=20(staff) groups=20(staff),502(awagent_enrolled),501(awagent),12(everyone),61(localaccounts),79(_appserverusr),80(admin),81(_appserveradm),98(_lpadmin),701(com.apple.sharepoint.group.1),33(_appstore),100(_lpoperator),204(_developer),250(_analyticsusers),395(com.apple.access_ftp),398(com.apple.access_screensharing),399(com.apple.access_ssh),400(com.apple.access_remote_ae)
arg -> config -> env, and the value is fully independent from ZPA's
. All ZCell APIs now receive the shared config and resolve the
id in each method.

Also document ZCell in README.md and docsrc/index.rst (auth section,
product lists, pagination table), add per-module ZCell doc stubs, fix a
pre-existing malformed FedRAMP grid table, and correct ZCell docstring
indentation so the Sphinx build is clean.

Updates CHANGELOG.md and CLAUDE.md accordingly.
@willguibr willguibr self-assigned this Jul 6, 2026
@willguibr willguibr added 🐛 type/bug :bug: type/bug documentation Improvements or additions to documentation ⚙️ In development ⚙️ Under active development 🆕 new-acceptance-tests New acceptance tests ZIA New API Resources ZIA New API Resources ZPA New API Resources ZPA New API Resources labels Jul 6, 2026
@willguibr willguibr moved this to ⚙️ In development in Zscaler Automation Dashboard 🛣 Jul 6, 2026
@willguibr willguibr merged commit 46d6f59 into master Jul 6, 2026
72 of 73 checks passed
@github-project-automation github-project-automation Bot moved this from ⚙️ In development to 🚀 Shipped in Zscaler Automation Dashboard 🛣 Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🐛 type/bug :bug: type/bug documentation Improvements or additions to documentation ⚙️ In development ⚙️ Under active development 🆕 new-acceptance-tests New acceptance tests ZIA New API Resources ZIA New API Resources ZPA New API Resources ZPA New API Resources

Projects

Status: 🚀 Shipped

Development

Successfully merging this pull request may close these issues.

1 participant