Skip to content

Fix use_keyring support in build command and TM1 integration#131

Merged
nicolasbisurgi merged 2 commits intomasterfrom
fix/use-keyring-tm1-integration
Mar 27, 2026
Merged

Fix use_keyring support in build command and TM1 integration#131
nicolasbisurgi merged 2 commits intomasterfrom
fix/use-keyring-tm1-integration

Conversation

@nicolasbisurgi
Copy link
Copy Markdown
Collaborator

Summary

  • Fixes use_keyring for tm1_integration #129: use_keyring config option was only handled in the main execution path but missing from rushti build and connect_to_tm1_instance
  • Extracts a shared resolve_tm1_params() helper in tm1_integration.py that centralizes keyring password resolution and non-TM1Service param cleanup (use_keyring, session_context, connection_file)
  • All three TM1 connection paths now go through the same logic, preventing future inconsistencies

Test plan

  • Run rushti build with use_keyring=true in config.ini and verify cube/dimension creation succeeds
  • Run a workflow from the RushTI cube (--tm1-instance with use_keyring=true) and verify task execution succeeds
  • Run standard task execution (from file) with use_keyring=true and verify it still works
  • Run standard task execution with password directly in config (no keyring) and verify no regression
  • Unit tests pass: python -m pytest tests/unit/ -x -q

🤖 Generated with Claude Code

nicolasbisurgi and others added 2 commits March 26, 2026 18:50
Resolves #129. The use_keyring config option was only handled in the
main execution path but missing from rushti build and
connect_to_tm1_instance. Extract shared resolve_tm1_params() helper
to centralize keyring resolution and non-TM1Service param cleanup.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The top-level `import keyring` in tm1_integration.py fails in CI where
no keyring backend is installed. Move to a lazy import inside
resolve_tm1_params (only when use_keyring is actually enabled). Also
set up getboolean/get mocks in test_connect_success so the mock
ConfigParser works with resolve_tm1_params.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@nicolasbisurgi nicolasbisurgi added the release:patch Triggers patch version bump (e.g.: 1.4.9 → 1.4.10) label Mar 26, 2026
@nicolasbisurgi nicolasbisurgi self-assigned this Mar 26, 2026
@nicolasbisurgi nicolasbisurgi merged commit b749989 into master Mar 27, 2026
9 checks passed
@nicolasbisurgi nicolasbisurgi deleted the fix/use-keyring-tm1-integration branch March 27, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:patch Triggers patch version bump (e.g.: 1.4.9 → 1.4.10)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

use_keyring for tm1_integration

1 participant