Merged
Conversation
Contributor
|
This PR is targeting If this is a regular feature/fix PR, please change the base branch to Current base: |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughVersion increment to 0.3.56 with OpenAPI spec update from v0.9.29 to v0.10.14, adding guest management endpoints, retry policies, execution region support, timezone handling for schedules, and enhanced parameter management tooling. Config error handling now distinguishes IO errors from configuration directory issues. Changes
Possibly Related PRs
Suggested Reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
konstantinoscs
force-pushed
the
chore/regen-clients
branch
from
b3488cf to
e98096a
Compare
konstantinoscs
force-pushed
the
chore/regen-clients
branch
3 times, most recently
from
2c5ab76 to
9fff0f0
Compare
konstantinoscs
force-pushed
the
chore/regen-clients
branch
from
9fff0f0 to
75050f4
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 13
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
crates/tower-api/src/models/run_run_initiator_details.rs (1)
20-22:⚠️ Potential issue | 🟡 MinorTypo in documentation comment: "initaited" → "initiated".
This appears to be carried over from the OpenAPI spec. Consider fixing at the spec level so future regenerations produce correct documentation.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@crates/tower-api/src/models/run_run_initiator_details.rs` around lines 20 - 22, Fix the typo in the documentation comment for the run_number field in RunRunInitiatorDetails: change "initaited" to "initiated" in the doc comment above pub run_number: Option<i64>; additionally, if this comment originates from the OpenAPI spec, update the spec definition so future codegen regenerations contain the corrected wording.
🧹 Nitpick comments (5)
src/tower/tower_api_client/models/update_schedule_params.py (1)
91-91: Redundant emptyupdate({})call.
field_dict.update({})is a no-op. This is likely an artifact of the code generator and has no functional impact.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/tower/tower_api_client/models/update_schedule_params.py` at line 91, The no-op call field_dict.update({}) inside the to_dict (or serialization) logic of UpdateScheduleParams should be removed; locate the update_schedule_params.py implementation (the to_dict/from_dict or dict building block where field_dict is assembled) and delete the redundant field_dict.update({}) line so the serialization logic is cleaner and unchanged otherwise.src/tower/tower_api_client/models/run_parameter.py (1)
19-42: Mirror optional semantics by defaultinghiddentoUNSET.At Line 24,
Falseas default causes unconditional"hidden": falseemission for new instances (Line 41-Line 42). For anUnset-aware field,UNSETis the safer default.Suggested change
- hidden (bool | Unset): Whether this parameter is hidden/secret. Defaults to false. Default: False. + hidden (bool | Unset): Whether this parameter is hidden/secret. Defaults to false when omitted. Default: UNSET. @@ - hidden: bool | Unset = False + hidden: bool | Unset = UNSET🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/tower/tower_api_client/models/run_parameter.py` around lines 19 - 42, The RunParameter model currently defaults the field hidden to False which forces "hidden": false into serialized output; change the declaration hidden: bool | Unset = UNSET (instead of False) so it mirrors the Unset-aware semantics and only emits "hidden" when explicitly set in to_dict; also update the field docstring/default note if present to reflect UNSET as the default. Ensure references to hidden in to_dict and any other methods (e.g., to_dict) continue to check for UNSET.src/tower/tower_api_client/models/parameter.py (1)
20-47: Alignhiddendefault with other optional boolean fields in the codebase.The
hiddenfield at line 26 defaults toFalseinstead ofUNSET, which is inconsistent with otherbool | Unsetfields in the codebase (e.g.,is_invitation_claimed,is_self_hosted_only,feature_updates). This causes fresh instances to always serialize"hidden": false(lines 46–47) rather than omitting the field when unset.Suggested change
- hidden: bool | Unset = False + hidden: bool | Unset = UNSET🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/tower/tower_api_client/models/parameter.py` around lines 20 - 47, The hidden field currently defaults to False causing it always to serialize; change the declaration of hidden in the Parameter model from "hidden: bool | Unset = False" to use the UNSET sentinel (e.g., "hidden: bool | Unset = UNSET") so it behaves like other optional booleans, ensure UNSET is imported/available in this module, and keep the existing to_dict check ("if hidden is not UNSET:") unchanged so unset values are omitted from serialization; update any tests or usages that assumed a default False if necessary.crates/tower-api/src/models/regenerate_guest_login_url_params.rs (1)
10-12: Unused imports in generated code.The imports
models,Deserializer, andDefaultOnNullare not used in this file. This is a minor issue typical of generated code templates. The#[serde_as]macro is applied but no fields useserde_as-specific attributes.♻️ Suggested cleanup (optional)
-use crate::models; -use serde::{Deserialize, Deserializer, Serialize}; -use serde_with::{serde_as, DefaultOnNull}; +use serde::{Deserialize, Serialize}; -#[serde_as] #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@crates/tower-api/src/models/regenerate_guest_login_url_params.rs` around lines 10 - 12, Remove the unused imports and unused macro attribute: delete the unused `use crate::models;`, `use serde::Deserializer;`, and `use serde_with::DefaultOnNull;` lines and remove the `#[serde_as]` attribute if none of the struct fields use serde_as-specific attributes (refer to the top of the file where `serde_as` is applied and the import lines for `models`, `Deserializer`, and `DefaultOnNull`); keep only `use serde::{Deserialize, Serialize};` and any imports actually referenced by the struct to eliminate the unused-import warnings.crates/tower-api/src/models/create_guest_params.rs (1)
20-23:DefaultOnNullon requiredappfield may mask invalid data.The
appfield is documented as required (it's the only parameter tonew()), butDefaultOnNullwill silently convert anullvalue to an empty string during deserialization. Combined with#[derive(Default)], this allows creating instances with an emptyappstring.For a request params struct, this is less critical since it flows client→server, but be aware that deserialization from JSON
{"app": null}will succeed withapp = ""rather than failing.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@crates/tower-api/src/models/create_guest_params.rs` around lines 20 - 23, The app field in CreateGuestParams currently uses #[serde_as(as = "DefaultOnNull")] which silently converts JSON null into an empty String; remove that attribute from the pub app: String declaration so deserialization will fail on null, and add an explicit runtime check in CreateGuestParams::new() (or wherever instances are constructed) to reject empty strings (return Err or panic as appropriate) to ensure callers can't create instances with an empty app; also consider removing/adjusting any #[derive(Default)] usage that permits empty default instances if unintended.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@crates/tower-api/src/apis/default_api.rs`:
- Around line 2320-2326: The enum UpdateOrganizationError (and the other enums
CreateSecretError, DeployAppError, DescribeRunError, DescribeRunGraphError,
UpdateMyTeamInvitationError) uses multiple status-specific variants that all
wrap models::ErrorModel and are annotated with #[serde(untagged)], causing any
matching body to always deserialize to the first variant; replace those
status-specific variants (Status403, Status404, Status409, Status422, Status500)
with a single DefaultResponse(models::ErrorModel) variant (keep
UnknownValue(serde_json::Value) if present) so the enum represents a default
error body rather than a misleading status-labeled variant; update any code that
constructs or matches these error enums to use DefaultResponse instead of
status-specific names.
In `@crates/tower-api/src/models/parameter.rs`:
- Around line 23-25: The doc comment for the field pub hidden: Option<bool> is
misleading — it currently says "Defaults to false" while the type actually omits
the field when None; update the comment to state that hidden is an Option<bool>
that is omitted when None (i.e., not serialized as an explicit false) and
document how consumers should treat a missing value, and apply the same wording
update to any other Option<bool> fields in the same struct (replace the
incorrect "Defaults to false" phrasing with "omitted when None / not serialized"
and note the effective behavior).
In `@src/tower/tower_api_client/api/default/delete_guest.py`:
- Around line 26-35: The _parse_response function is calling response.json() for
a 204 No Content response which can raise JSONDecodeError; update
_parse_response to first check response.status_code == 204 and then verify
response.content (or response.text) is non-empty before calling response.json(),
returning an appropriate empty DeleteGuestOutputBody (or using
DeleteGuestOutputBody.from_dict({}) only when content exists) for the 204 path;
for the default path ensure ErrorModel.from_dict is only called when
response.content is present. Reference: _parse_response, DeleteGuestOutputBody,
ErrorModel.
In `@src/tower/tower_api_client/api/default/update_organization.py`:
- Line 39: The typed/detailed response wrappers (e.g., the functions handling
the UpdateOrganization endpoint such as update_organization, sync_detailed,
async_detailed or any helper that returns UpdateOrganizationResponse) currently
document/annotate return types as ErrorModel | UpdateOrganizationResponse but
the diff adds a valid None parse-path; update all relevant type hints and
docstrings to include None (ErrorModel | UpdateOrganizationResponse | None) and
adjust any return annotations/TypedDicts or response wrapper classes to reflect
None as a possible parsed value so the SDK contract matches the new parsing
behavior.
In `@src/tower/tower_api_client/models/api_key.py`:
- Around line 94-100: The expires_at deserialization doesn't guard for null and
calls isoparse on None; update the block handling _expires_at to mirror
last_used_at: treat None as a valid value and only call isoparse for non-null,
non-UNSET values, and change the type annotation for expires_at to
datetime.datetime | None | Unset so None is allowed; adjust the variables
_expires_at, expires_at and the isoparse call accordingly in the ApiKey model.
In `@src/tower/tower_api_client/models/create_guest_params.py`:
- Line 68: In from_dict() of the CreateGuestParams model, preserve the declared
default for the expires_in field instead of falling back to UNSET; change the
extraction to pop "expires_in" with the model default (259200) so deserializing
a dict without expires_in retains the default value (i.e., use expires_in =
d.pop("expires_in", 259200) within CreateGuestParams.from_dict()).
In `@src/tower/tower_api_client/models/invite_team_member_params.py`:
- Around line 61-62: The from_dict deserializer for InviteTeamMemberParams uses
d.pop("role") which raises KeyError when "role" is missing; update
InviteTeamMemberParams.from_dict to supply a default by popping with a default
(use InviteTeamMemberParamsRole.DEVELOPER or its value) and then construct the
enum via InviteTeamMemberParamsRole(...), e.g., retrieve role_value =
d.pop("role", InviteTeamMemberParamsRole.DEVELOPER) and then set role =
InviteTeamMemberParamsRole(role_value) so the class-level default is respected
and missing keys don't error.
In `@src/tower/tower_api_client/models/list_runs_status_item.py`:
- Line 10: Add the new "retrying" state into the run-awaiting logic and
reconcile enum members: update _is_run_awaiting_completion in
src/tower/_client.py to treat "retrying" the same as "pending", "scheduled", and
"running" (i.e., consider it awaiting completion), and modify ListRunsStatusItem
(class/enum in list_runs_status_item.py) to include the "scheduled" member so it
matches RunStatus and the checks in _is_run_awaiting_completion; ensure any
switch/if lists that enumerate active states use a single canonical source or
include both "scheduled" and "retrying" consistently.
In `@src/tower/tower_api_client/models/regenerate_guest_login_url_params.py`:
- Around line 25-26: In regenerate_guest_login_url_params.py the attribute
expires_in has a declared default of 259200 but from_dict() currently uses UNSET
when the key is missing, causing inconsistent instances; update from_dict() (the
method that pops/reads "expires_in" from the input dict) to use 259200 as the
default when the key is absent (or when the popped value equals UNSET) and
coerce to int | Unset as the class expects, so the object created via
from_dict() matches the class-level default for expires_in.
In `@src/tower/tower_api_client/models/run_attempt.py`:
- Around line 68-79: The parser currently silently returns the original `data`
cast as a datetime when parsing fails in `_parse_ended_at` (and similarly in
`_parse_started_at`), which can mask malformed inputs; change the logic to not
fall back to `cast(...)` but instead raise a clear exception (e.g., ValueError
or TypeError) that includes the field name ("ended_at" / "started_at") and the
offending `data` value, or explicitly return None if the model should accept
missing values; update the except block to either re-raise a descriptive
exception or return None and remove the final `return cast(...)` so invalid
types are not silently accepted.
In `@src/tower/tower_api_client/models/run_results.py`:
- Around line 76-77: The parsing currently does d.pop("retrying") which will
raise KeyError for payloads missing that field; update the parsing in the
RunResults (or relevant from_dict/parse method where retrying is extracted) to
use a safe default like d.pop("retrying", False) or d.get("retrying", False) and
then cast/validate as needed so older payloads without "retrying" parse
successfully; ensure any downstream use of the retrying variable still expects
the same boolean type.
In `@src/tower/tower_api_client/models/run.py`:
- Around line 296-301: The code treating _retry_policy uses isinstance(...,
Unset) but doesn't handle JSON null (None), so RunRetryPolicy.from_dict(None)
will raise; update the branch in the deserialization for retry_policy (variable
names: _retry_policy, retry_policy) to treat None the same as UNSET (or
explicitly check for None) before calling RunRetryPolicy.from_dict, e.g., if
_retry_policy is UNSET or _retry_policy is None then set retry_policy = UNSET,
otherwise call RunRetryPolicy.from_dict(_retry_policy).
- Around line 285-293: The deserialization in models/run.py assumes _attempts is
iterable but if the API returns "attempts": null then _attempts will be None and
the for-loop in the Run model will raise a TypeError; update the check around
_attempts (in the Run.from_dict or equivalent deserialization block that sets
attempts) to explicitly guard against None (e.g., require _attempts is not UNSET
and _attempts is not None or check isinstance(_attempts, list)) before
iterating, and apply the same defensive change to the analogous pattern in other
models such as error_model.py to avoid NoneType iteration errors.
---
Outside diff comments:
In `@crates/tower-api/src/models/run_run_initiator_details.rs`:
- Around line 20-22: Fix the typo in the documentation comment for the
run_number field in RunRunInitiatorDetails: change "initaited" to "initiated" in
the doc comment above pub run_number: Option<i64>; additionally, if this comment
originates from the OpenAPI spec, update the spec definition so future codegen
regenerations contain the corrected wording.
---
Nitpick comments:
In `@crates/tower-api/src/models/create_guest_params.rs`:
- Around line 20-23: The app field in CreateGuestParams currently uses
#[serde_as(as = "DefaultOnNull")] which silently converts JSON null into an
empty String; remove that attribute from the pub app: String declaration so
deserialization will fail on null, and add an explicit runtime check in
CreateGuestParams::new() (or wherever instances are constructed) to reject empty
strings (return Err or panic as appropriate) to ensure callers can't create
instances with an empty app; also consider removing/adjusting any
#[derive(Default)] usage that permits empty default instances if unintended.
In `@crates/tower-api/src/models/regenerate_guest_login_url_params.rs`:
- Around line 10-12: Remove the unused imports and unused macro attribute:
delete the unused `use crate::models;`, `use serde::Deserializer;`, and `use
serde_with::DefaultOnNull;` lines and remove the `#[serde_as]` attribute if none
of the struct fields use serde_as-specific attributes (refer to the top of the
file where `serde_as` is applied and the import lines for `models`,
`Deserializer`, and `DefaultOnNull`); keep only `use serde::{Deserialize,
Serialize};` and any imports actually referenced by the struct to eliminate the
unused-import warnings.
In `@src/tower/tower_api_client/models/parameter.py`:
- Around line 20-47: The hidden field currently defaults to False causing it
always to serialize; change the declaration of hidden in the Parameter model
from "hidden: bool | Unset = False" to use the UNSET sentinel (e.g., "hidden:
bool | Unset = UNSET") so it behaves like other optional booleans, ensure UNSET
is imported/available in this module, and keep the existing to_dict check ("if
hidden is not UNSET:") unchanged so unset values are omitted from serialization;
update any tests or usages that assumed a default False if necessary.
In `@src/tower/tower_api_client/models/run_parameter.py`:
- Around line 19-42: The RunParameter model currently defaults the field hidden
to False which forces "hidden": false into serialized output; change the
declaration hidden: bool | Unset = UNSET (instead of False) so it mirrors the
Unset-aware semantics and only emits "hidden" when explicitly set in to_dict;
also update the field docstring/default note if present to reflect UNSET as the
default. Ensure references to hidden in to_dict and any other methods (e.g.,
to_dict) continue to check for UNSET.
In `@src/tower/tower_api_client/models/update_schedule_params.py`:
- Line 91: The no-op call field_dict.update({}) inside the to_dict (or
serialization) logic of UpdateScheduleParams should be removed; locate the
update_schedule_params.py implementation (the to_dict/from_dict or dict building
block where field_dict is assembled) and delete the redundant
field_dict.update({}) line so the serialization logic is cleaner and unchanged
otherwise.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f4f960d4-e813-46a0-b77f-20de3e1b2ab3
📒 Files selected for processing (271)
crates/tower-api/README.mdcrates/tower-api/src/apis/configuration.rscrates/tower-api/src/apis/default_api.rscrates/tower-api/src/apis/feature_flags_api.rscrates/tower-api/src/models/account.rscrates/tower-api/src/models/acknowledge_alert_response.rscrates/tower-api/src/models/acknowledge_all_alerts_response.rscrates/tower-api/src/models/alert.rscrates/tower-api/src/models/api_key.rscrates/tower-api/src/models/app.rscrates/tower-api/src/models/app_statistics.rscrates/tower-api/src/models/app_summary.rscrates/tower-api/src/models/app_version.rscrates/tower-api/src/models/authentication_context.rscrates/tower-api/src/models/batch_schedule_params.rscrates/tower-api/src/models/batch_schedule_response.rscrates/tower-api/src/models/cancel_run_response.rscrates/tower-api/src/models/catalog.rscrates/tower-api/src/models/catalog_property.rscrates/tower-api/src/models/claim_device_login_ticket_params.rscrates/tower-api/src/models/claim_device_login_ticket_response.rscrates/tower-api/src/models/create_account_params.rscrates/tower-api/src/models/create_account_params_flags_struct.rscrates/tower-api/src/models/create_account_response.rscrates/tower-api/src/models/create_api_key_params.rscrates/tower-api/src/models/create_api_key_response.rscrates/tower-api/src/models/create_app_params.rscrates/tower-api/src/models/create_app_response.rscrates/tower-api/src/models/create_authenticator_params.rscrates/tower-api/src/models/create_authenticator_response.rscrates/tower-api/src/models/create_catalog_params.rscrates/tower-api/src/models/create_catalog_response.rscrates/tower-api/src/models/create_device_login_ticket_response.rscrates/tower-api/src/models/create_environment_params.rscrates/tower-api/src/models/create_environment_response.rscrates/tower-api/src/models/create_guest_params.rscrates/tower-api/src/models/create_guest_response.rscrates/tower-api/src/models/create_password_reset_params.rscrates/tower-api/src/models/create_password_reset_response.rscrates/tower-api/src/models/create_sandbox_secrets_params.rscrates/tower-api/src/models/create_sandbox_secrets_response.rscrates/tower-api/src/models/create_schedule_params.rscrates/tower-api/src/models/create_schedule_response.rscrates/tower-api/src/models/create_secret_params.rscrates/tower-api/src/models/create_secret_response.rscrates/tower-api/src/models/create_session_params.rscrates/tower-api/src/models/create_session_response.rscrates/tower-api/src/models/create_team_params.rscrates/tower-api/src/models/create_team_response.rscrates/tower-api/src/models/create_webhook_params.rscrates/tower-api/src/models/create_webhook_response.rscrates/tower-api/src/models/delete_api_key_params.rscrates/tower-api/src/models/delete_api_key_response.rscrates/tower-api/src/models/delete_app_response.rscrates/tower-api/src/models/delete_authenticator_params.rscrates/tower-api/src/models/delete_authenticator_response.rscrates/tower-api/src/models/delete_catalog_response.rscrates/tower-api/src/models/delete_guest_output_body.rscrates/tower-api/src/models/delete_schedule_params.rscrates/tower-api/src/models/delete_schedule_response.rscrates/tower-api/src/models/delete_secret_response.rscrates/tower-api/src/models/delete_session_params.rscrates/tower-api/src/models/delete_session_response.rscrates/tower-api/src/models/delete_team_invitation_params.rscrates/tower-api/src/models/delete_team_invitation_response.rscrates/tower-api/src/models/delete_team_params.rscrates/tower-api/src/models/delete_team_response.rscrates/tower-api/src/models/delete_webhook_response.rscrates/tower-api/src/models/deploy_app_request.rscrates/tower-api/src/models/deploy_app_response.rscrates/tower-api/src/models/describe_account_body.rscrates/tower-api/src/models/describe_app_response.rscrates/tower-api/src/models/describe_app_version_response.rscrates/tower-api/src/models/describe_authentication_context_body.rscrates/tower-api/src/models/describe_device_login_session_response.rscrates/tower-api/src/models/describe_email_preferences_body.rscrates/tower-api/src/models/describe_plan_response.rscrates/tower-api/src/models/describe_run_graph_response.rscrates/tower-api/src/models/describe_run_links.rscrates/tower-api/src/models/describe_run_logs_response.rscrates/tower-api/src/models/describe_run_response.rscrates/tower-api/src/models/describe_secrets_key_response.rscrates/tower-api/src/models/describe_session_response.rscrates/tower-api/src/models/describe_team_response.rscrates/tower-api/src/models/describe_webhook_response.rscrates/tower-api/src/models/email_subscriptions.rscrates/tower-api/src/models/encrypted_catalog_property.rscrates/tower-api/src/models/environment.rscrates/tower-api/src/models/error_detail.rscrates/tower-api/src/models/error_model.rscrates/tower-api/src/models/event_alert.rscrates/tower-api/src/models/event_error.rscrates/tower-api/src/models/event_log.rscrates/tower-api/src/models/event_shouldertap.rscrates/tower-api/src/models/event_warning.rscrates/tower-api/src/models/export_catalogs_params.rscrates/tower-api/src/models/export_catalogs_response.rscrates/tower-api/src/models/export_secrets_params.rscrates/tower-api/src/models/export_secrets_response.rscrates/tower-api/src/models/exported_catalog.rscrates/tower-api/src/models/exported_catalog_property.rscrates/tower-api/src/models/exported_secret.rscrates/tower-api/src/models/feature.rscrates/tower-api/src/models/featurebase_identity.rscrates/tower-api/src/models/generate_app_statistics_response.rscrates/tower-api/src/models/generate_authenticator_response.rscrates/tower-api/src/models/generate_run_statistics_response.rscrates/tower-api/src/models/generate_runner_credentials_response.rscrates/tower-api/src/models/get_feature_flag_response_body.rscrates/tower-api/src/models/guest.rscrates/tower-api/src/models/invite_team_member_params.rscrates/tower-api/src/models/invite_team_member_response.rscrates/tower-api/src/models/leave_team_response.rscrates/tower-api/src/models/list_alerts_response.rscrates/tower-api/src/models/list_api_keys_response.rscrates/tower-api/src/models/list_app_environments_response.rscrates/tower-api/src/models/list_app_versions_response.rscrates/tower-api/src/models/list_apps_response.rscrates/tower-api/src/models/list_authenticators_response.rscrates/tower-api/src/models/list_catalogs_response.rscrates/tower-api/src/models/list_environments_response.rscrates/tower-api/src/models/list_guests_response.rscrates/tower-api/src/models/list_my_team_invitations_response.rscrates/tower-api/src/models/list_runners_response.rscrates/tower-api/src/models/list_runs_response.rscrates/tower-api/src/models/list_schedules_response.rscrates/tower-api/src/models/list_secret_environments_response.rscrates/tower-api/src/models/list_secrets_response.rscrates/tower-api/src/models/list_team_invitations_response.rscrates/tower-api/src/models/list_team_members_response.rscrates/tower-api/src/models/list_teams_response.rscrates/tower-api/src/models/list_webhooks_response.rscrates/tower-api/src/models/mod.rscrates/tower-api/src/models/organization.rscrates/tower-api/src/models/organization_usage.rscrates/tower-api/src/models/pagination.rscrates/tower-api/src/models/parameter.rscrates/tower-api/src/models/plan.rscrates/tower-api/src/models/refresh_session_params.rscrates/tower-api/src/models/refresh_session_response.rscrates/tower-api/src/models/regenerate_guest_login_url_params.rscrates/tower-api/src/models/regenerate_guest_login_url_response.rscrates/tower-api/src/models/remove_team_member_params.rscrates/tower-api/src/models/remove_team_member_response.rscrates/tower-api/src/models/resend_team_invitation_params.rscrates/tower-api/src/models/resend_team_invitation_response.rscrates/tower-api/src/models/run.rscrates/tower-api/src/models/run_app_initiator_data.rscrates/tower-api/src/models/run_app_params.rscrates/tower-api/src/models/run_app_response.rscrates/tower-api/src/models/run_attempt.rscrates/tower-api/src/models/run_failure_alert.rscrates/tower-api/src/models/run_graph_node.rscrates/tower-api/src/models/run_graph_run_id.rscrates/tower-api/src/models/run_initiator.rscrates/tower-api/src/models/run_initiator_details.rscrates/tower-api/src/models/run_log_line.rscrates/tower-api/src/models/run_parameter.rscrates/tower-api/src/models/run_results.rscrates/tower-api/src/models/run_retry_policy.rscrates/tower-api/src/models/run_run_initiator_details.rscrates/tower-api/src/models/run_statistics.rscrates/tower-api/src/models/run_timeseries_point.rscrates/tower-api/src/models/runner.rscrates/tower-api/src/models/runner_credentials.rscrates/tower-api/src/models/schedule.rscrates/tower-api/src/models/schedule_run_initiator_details.rscrates/tower-api/src/models/search_runs_response.rscrates/tower-api/src/models/secret.rscrates/tower-api/src/models/server_sent_events_inner.rscrates/tower-api/src/models/server_sent_events_inner_1.rscrates/tower-api/src/models/server_sent_events_inner_2.rscrates/tower-api/src/models/session.rscrates/tower-api/src/models/shoulder_tap.rscrates/tower-api/src/models/sse_warning.rscrates/tower-api/src/models/statistics_settings.rscrates/tower-api/src/models/team.rscrates/tower-api/src/models/team_invitation.rscrates/tower-api/src/models/team_membership.rscrates/tower-api/src/models/test_webhook_response.rscrates/tower-api/src/models/token.rscrates/tower-api/src/models/unverified_authenticator.rscrates/tower-api/src/models/update_account_params.rscrates/tower-api/src/models/update_account_response.rscrates/tower-api/src/models/update_app_params.rscrates/tower-api/src/models/update_app_response.rscrates/tower-api/src/models/update_catalog_params.rscrates/tower-api/src/models/update_catalog_response.rscrates/tower-api/src/models/update_email_preferences_body.rscrates/tower-api/src/models/update_environment_params.rscrates/tower-api/src/models/update_environment_response.rscrates/tower-api/src/models/update_my_team_invitation_params.rscrates/tower-api/src/models/update_my_team_invitation_response.rscrates/tower-api/src/models/update_organization_params.rscrates/tower-api/src/models/update_organization_response.rscrates/tower-api/src/models/update_password_reset_params.rscrates/tower-api/src/models/update_password_reset_response.rscrates/tower-api/src/models/update_plan_params.rscrates/tower-api/src/models/update_plan_response.rscrates/tower-api/src/models/update_schedule_params.rscrates/tower-api/src/models/update_schedule_response.rscrates/tower-api/src/models/update_secret_params.rscrates/tower-api/src/models/update_secret_response.rscrates/tower-api/src/models/update_team_member_params.rscrates/tower-api/src/models/update_team_member_response.rscrates/tower-api/src/models/update_team_params.rscrates/tower-api/src/models/update_team_response.rscrates/tower-api/src/models/update_user_params.rscrates/tower-api/src/models/update_user_response.rscrates/tower-api/src/models/update_webhook_params.rscrates/tower-api/src/models/update_webhook_response.rscrates/tower-api/src/models/usage_limit.rscrates/tower-api/src/models/user.rscrates/tower-api/src/models/verified_authenticator.rscrates/tower-api/src/models/verify_email_params.rscrates/tower-api/src/models/verify_email_response.rscrates/tower-api/src/models/webhook.rscrates/tower-cmd/src/api.rscrates/tower-cmd/src/apps.rscrates/tower-cmd/src/mcp.rssrc/tower/tower_api_client/api/default/create_guest.pysrc/tower/tower_api_client/api/default/delete_guest.pysrc/tower/tower_api_client/api/default/describe_organization_usage.pysrc/tower/tower_api_client/api/default/leave_team.pysrc/tower/tower_api_client/api/default/list_guests.pysrc/tower/tower_api_client/api/default/list_teams.pysrc/tower/tower_api_client/api/default/regenerate_guest_login_url.pysrc/tower/tower_api_client/api/default/update_organization.pysrc/tower/tower_api_client/models/__init__.pysrc/tower/tower_api_client/models/account.pysrc/tower/tower_api_client/models/api_key.pysrc/tower/tower_api_client/models/app.pysrc/tower/tower_api_client/models/create_api_key_params.pysrc/tower/tower_api_client/models/create_guest_params.pysrc/tower/tower_api_client/models/create_guest_response.pysrc/tower/tower_api_client/models/create_schedule_params.pysrc/tower/tower_api_client/models/delete_guest_output_body.pysrc/tower/tower_api_client/models/describe_run_links.pysrc/tower/tower_api_client/models/generate_run_statistics_status_item.pysrc/tower/tower_api_client/models/guest.pysrc/tower/tower_api_client/models/invite_team_member_params.pysrc/tower/tower_api_client/models/invite_team_member_params_role.pysrc/tower/tower_api_client/models/list_guests_response.pysrc/tower/tower_api_client/models/list_runs_status_item.pysrc/tower/tower_api_client/models/organization_usage.pysrc/tower/tower_api_client/models/parameter.pysrc/tower/tower_api_client/models/regenerate_guest_login_url_params.pysrc/tower/tower_api_client/models/regenerate_guest_login_url_response.pysrc/tower/tower_api_client/models/run.pysrc/tower/tower_api_client/models/run_app_params.pysrc/tower/tower_api_client/models/run_attempt.pysrc/tower/tower_api_client/models/run_log_line.pysrc/tower/tower_api_client/models/run_parameter.pysrc/tower/tower_api_client/models/run_results.pysrc/tower/tower_api_client/models/run_retry_policy.pysrc/tower/tower_api_client/models/run_status.pysrc/tower/tower_api_client/models/run_timeseries_point.pysrc/tower/tower_api_client/models/runner.pysrc/tower/tower_api_client/models/schedule.pysrc/tower/tower_api_client/models/search_runs_status_item.pysrc/tower/tower_api_client/models/team.pysrc/tower/tower_api_client/models/team_invitation.pysrc/tower/tower_api_client/models/update_account_params.pysrc/tower/tower_api_client/models/update_account_params_execution_region.pysrc/tower/tower_api_client/models/update_app_params.pysrc/tower/tower_api_client/models/update_schedule_params.pysrc/tower/tower_api_client/models/update_team_params.pysrc/tower/tower_api_client/models/update_team_params_execution_region.pysrc/tower/tower_api_client/models/usage_limit.pytests/mock-api-server/main.pytests/tower/test_client.py
socksy
approved these changes
Apr 1, 2026
Merged
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just regenerating clients
Summary by CodeRabbit
Release Notes
New Features
Improvements