cloudshell-firewall-panos 3.1.1

Allow cloudshell-cli 6.x so telnet works on Python 3.13 (v3.1.1) (#15)

cloudshell-cli 5.x imports telnetlib unguarded, which is gone in 3.13,
so telnet sessions failed at import time even though the package
installed cleanly. cli 6.0.0 vendors telnetlib and is otherwise
API-identical to 5.0.2, so the pin is widened rather than forced.

Juniper additionally caps pydantic to ~=1.10 (matching PanOS): via
cloudshell-shell-connectivity-flow~=4.0's pydantic<2.5, the resolver
would pick pydantic 2.4 -> pydantic-core 2.10.1, which has no cp313
wheel and fails to build.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

cloudshell-firewall-panos 3.1.0

Adopt cloudshell-snmp 6.0 / cloudshell-snmp-autoload 3.0 (#14)

- cloudshell-snmp >=6.0,<7.0 and cloudshell-snmp-autoload >=3.0,<4.0
  (pysnmp 7 based; APIs drop-in compatible, no source changes needed)
- pin pydantic~=1.10: pydantic 2.4 (max allowed by
  cloudshell-shell-connectivity-flow~=4.0) has no Python 3.13 wheels
- python_requires>=3.9 with 3.9-3.13 classifiers
- ignore flake8 I900 (flake8-requirements false positives on the new
  version-range pins)
- version 3.0.0 -> 3.1.0

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

cloudshell-firewall-panos 3.0.0

• Updated to the latest infrastructure.

cloudshell-firewall-panos 2.0.1

• Fix return correct filename from save command

cloudshell-firewall-panos 2.0.0

Python 3 support for Palo Alto Shells

CloudShell Firewall PanOS

MIBs updated.
Changed save startup configuration logic

CloudShell Firewall PanOS

[BugFix 40245] Fixed issue with save\restore failing on PanOS7.1

CloudShell Firewall PanOS

MIBs update

CloudShell Firewall PanOS

1.0.0

initial commit