from __future__ import absolute_import # import models into sdk package from .models.branch_command import BranchCommand from .models.branches_command import BranchesCommand from .models.change_command import ChangeCommand from .models.changes_command import ChangesCommand from .models.changelist_request import ChangelistRequest from .models.changelist_action import ChangelistAction from .models.client_command import ClientCommand from .models.clients_command import ClientsCommand from .models.command_response import CommandResponse from .models.command_request import CommandRequest from .models.counter import Counter from .models.depot_command import DepotCommand from .models.depots_command import DepotsCommand from .models.dirs_command import DirsCommand from .models.files_command import FilesCommand from .models.fstat_command import FstatCommand from .models.git_fusion_repo_id import GitFusionRepoId from .models.git_fusion_repo_config import GitFusionRepoConfig from .models.git_fusion_repo_branch_config import GitFusionRepoBranchConfig from .models.git_fusion_repo_global_overrides import GitFusionRepoGlobalOverrides from .models.group_command import GroupCommand from .models.groups_command import GroupsCommand from .models.hws_status import HWSStatus from .models.labels_command import LabelsCommand from .models.label_command import LabelCommand from .models.location import Location from .models.login_request import LoginRequest from .models.server_login_request import ServerLoginRequest from .models.login_response import LoginResponse from .models.p4d_config_id import P4dConfigId from .models.protections import Protections from .models.servers_command import ServersCommand from .models.server_command import ServerCommand from .models.stream_command import StreamCommand from .models.streams_command import StreamsCommand from .models.triggers import Triggers from .models.user_command import UserCommand from .models.users_command import UsersCommand from .models.job_command import JobCommand from .models.jobs_command import JobsCommand # import apis into sdk package from .apis.alpha_api import AlphaApi from .apis.default_api import DefaultApi # import ApiClient from .api_client import ApiClient from .configuration import Configuration configuration = Configuration()
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/python/helix_web_services_client/__init__.py | |||||
#4 | 19307 | tjuricek |
Python Client SDK tests from counters to users Need to treat the job-related models as UserDict instances, which involves some adjustments to the Swagger code generators. |
||
#3 | 19202 | tjuricek | Revised documentation for the Ruby Client SDK; removed obsolete methods and definitions, and restyled a lot of the tables. | ||
#2 | 19002 | tjuricek |
Improve API to interact with multiple p4ds. The configuration now requires an explicit setting of what P4Ds HWS can talk to via the 'P4D config dir', where there's a file indicating connection settings per p4d, and importantly, an ID. This is the "server ID" referenced everywhere. Most methods now require a server ID to indicate which p4d to manipulate. In the future, it's likely we will interact with *multiple* p4d instances on some services. This completely removes the ability to run HWS as a kind of an "open proxy" to whatever p4d you want. Given the nature of the change and the lack of priority, we've removed Helix Cloud testing and disabled several methods from their "Helix Cloud" implementation. These will be relatively easy to bring back, we'll just need a new method from Raymond that lists the "allowed server IDs" that map to the HWS configured server IDs for a particular user. Another notable aspect of this change is the use of JSON Web Token to create our authentication key. We associate this key with an in-memory "session" that contains the P4D tickets we use to authenticate users. The JWT token, by default, is assigned a timeout, which allows HWS to block further access to underlying servers without having to interact with multiple auth backends. If any backend fails with that session, the user will get a 403. If you disable the timeout, you'll need to ensure your clients clear out sessions. |
||
#1 | 18818 | tjuricek | Python Client SDK for Helix Web Services |