fix: handle missing lastModifiedBy in TrafficGRETunnel

.editorconfig

@@ -0,0 +1,21 @@
+# http://editorconfig.org
+
+root = true
+
+[*.py]
+indent_style = space
+indent_size = 4
+trim_trailing_whitespace = true
+insert_final_newline = true
+charset = utf-8
+end_of_line = lf
+
+[*.bat]
+indent_style = tab
+end_of_line = crlf
+
+[LICENSE]
+insert_final_newline = false
+
+[Makefile]
+indent_style = tab

.github/CODEOWNERS

@@ -0,0 +1 @@
+/.github/ @willguibr

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature Request
+about: Suggest a new feature or improvement for the Python SDK for Zscaler.
+title: "[FEATURE] "
+labels: ''
+assignees: ''
+
+---
+
+**Problem Statement**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Proposed Solution**
+A clear and concise description of what you want to happen.
+
+**Additional Context**
+Add any other context, references or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/sdk-issue.md

@@ -0,0 +1,32 @@
+---
+name: SDK Issue
+about: Use this to report an issue with the Python SDK for Zscaler.
+title: "[ISSUE] "
+labels: ''
+assignees: ''
+
+---
+
+**Description**
+A clear and concise description of what the bug is.
+
+**Reproduction**
+A minimal code sample demonstrating the bug.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Is it a regression?**
+Did this work in a previous version of the SDK? If so, which versions did you try?
+
+**Debug Logs**
+The SDK logs are helpful in debugging information when debug logging is enabled. Set the log level to debug by adding `logging.basicConfig(level=logging.DEBUG)` to your program, and include the logs here. You can also set the following environment variables in order to enable logging:
+* `ZSCALER_SDK_LOG` - Turn on logging
+* `ZSCALER_SDK_VERBOSE` - Turn on logging in verbose mode
+
+**Other Information**
+ - OS: [e.g. macOS]
+ - Version: [e.g. 0.1.0]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/sdk-v2-issue.md

@@ -0,0 +1,100 @@
+---
+name: SDK v2.x (Preview / Beta) Issue
+about: Report an issue specific to the data-driven Zscaler Python SDK v2.x (currently in public preview / beta).
+title: "[v2-ISSUE] "
+labels: 'v2-beta'
+assignees: ''
+
+---
+
+> ⚠️ **This template is for the Zscaler Python SDK v2.x preview/beta only.**
+> If you are using the stable **v1.x** line (`pip install zscaler-sdk-python`),
+> please use the [SDK Issue](./sdk-issue.md) template instead.
+>
+> v2.x is **OneAPI-only** — legacy authentication is **not** supported, and
+> not every product is covered yet. Please confirm you are using OneAPI
+> credentials (clientId / clientSecret + vanityDomain, or a bound API key)
+> before opening this issue.
+>
+> 📦 PyPI (pre-release):
+> https://pypi.org/project/zscaler-sdk-python/#history
+>
+> ```bash
+> pip install --pre --upgrade "zscaler-sdk-python>=2.0.0b1"
+> ```
+>
+> 📚 Getting started / docs (Zscaler Automation Hub):
+> https://automate.zscaler.com/docs/tools/sdk-documentation/sdk-getting-started
+>
+> 🔁 v1.x → v2.x migration guide:
+> https://github.com/zscaler/zscaler-sdk-python/blob/master/UPGRADE_GUIDE.md
+
+**SDK Version**
+Output of `pip show zscaler-sdk-python` (must be a `2.0.0bN` pre-release):
+
+```
+```
+
+**Affected Product / Service**
+Which Zscaler product and resource is affected? (e.g. ZIA / `pac_files`, ZPA / `application_segments`, ZDX / `devices`, ZIdentity / `users`, etc.)
+
+**Description**
+A clear and concise description of what the bug is.
+
+**Reproduction**
+A minimal, self-contained code sample demonstrating the bug. Please redact any
+real client IDs, secrets, vanity domains, or customer IDs.
+
+```python
+from zscaler import ZscalerClient
+
+config = {
+    "clientId": "<redacted>",
+    "clientSecret": "<redacted>",
+    "vanityDomain": "<redacted>",
+    # "customerId": "<redacted>",  # ZPA only
+    "cloud": "PRODUCTION",
+}
+
+with ZscalerClient(config) as client:
+    # ...
+    pass
+```
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Actual behavior**
+What actually happened. Include the full exception/traceback or API response,
+not just the message.
+
+**Is it a regression from v1.x?**
+Did the equivalent call work on the v1.x SDK? If so, which v1.x version?
+
+**Debug Logs**
+SDK debug logs are essential for triage. Enable them with one of:
+
+- Environment variables:
+  * `ZSCALER_SDK_LOG=true`
+  * `ZSCALER_SDK_VERBOSE=true`
+- Or in code:
+  ```python
+  import logging
+  logging.basicConfig(level=logging.DEBUG)
+  ```
+
+Paste the relevant request/response lines here (redact tokens and PII):
+
+```
+```
+
+**Environment**
+ - OS: [e.g. macOS 14.5, Ubuntu 22.04, Windows 11]
+ - Python version: [e.g. 3.11.8]
+ - SDK version: [e.g. 2.0.0b3]
+ - Auth mode: OneAPI (client credentials / API key)
+ - Cloud: [e.g. PRODUCTION, zscalertwo, zscalerthree, gov]
+
+**Additional context**
+Anything else that helps reproduce or scope the issue (related Automation Hub
+docs link, OpenAPI spec section, screenshots, etc.).

.github/dependabot.yml

@@ -0,0 +1,7 @@
+---
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: daily

.github/pull_request_template.md

@@ -0,0 +1,39 @@
+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 keywords[1].
+
+## 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.
+
+[1]: https://help.github.com/articles/closing-issues-using-keywords/

.github/set-version.sh

@@ -0,0 +1,43 @@
+#!/usr/bin/env bash
+
+SCRIPT_BASE="$(cd "$( dirname "$0")" && pwd )"
+ROOT=${SCRIPT_BASE}/..
+
+# Exit immediatly if any command exits with a non-zero status
+set -e
+
+# Usage
+print_usage() {
+    echo "Set the app/add-on version"
+    echo ""
+    echo "Usage:"
+    echo "  set-version.sh <new-version>"
+    echo ""
+}
+
+# if less than one arguments supplied, display usage
+if [  $# -lt 1 ]
+then
+    print_usage
+    exit 1
+fi
+
+# check whether user had supplied -h or --help . If yes display usage
+if [ "$1" == "--help" ] || [ "$1" == "-h" ]; then
+    print_usage
+    exit 0
+fi
+
+NEW_VERSION=$(echo "$1" | sed -e 's/-beta\./.b/' | sed -e 's/-alpha\./.a/')
+
+# Set version in pyproject.toml
+echo "Updating pyproject.toml"
+grep -E '^version = ".+"$' "$ROOT/pyproject.toml" || exit 1
+sed -i.bak -E "s/^version = \".+\"$/version = \"$1\"/" "$ROOT/pyproject.toml" && rm "$ROOT/pyproject.toml.bak"
+
+# Set version in __init__.py
+grep -E '^__version__ = ".+"$' "$ROOT/zscaler/__init__.py" >/dev/null
+sed -i.bak -E "s/^__version__ = \".+\"$/__version__ = \"$NEW_VERSION\"/" "$ROOT/zscaler/__init__.py" && rm "$ROOT/zscaler/__init__.py.bak"
+
+# Generate setup.py from pyproject.toml
+make sync-deps

.github/stale.yml

@@ -0,0 +1,18 @@
+---
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 180
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 30
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false