Multiple Profiles

Open
#1,575 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
50/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by tracing the library's PAT authentication entry point and how credentials are currently read before REST API calls. Define how named profiles and environment-variable fallback should behave, then add coverage showing profile selection and the token_name, personal_access_token, and site_id values used for authentication.

Written by the indexing model from the issue text.

Description

enhancement gap help wanted needs investigation

Summary

I would love it if tableau authentication behaved more like AWS

I obviously can build wrappers for this, but this seems like pretty common functionality in python api packages. (Databricks,DBT,AWS,etc)

Request Type

I don't believe this would affect or be affected at all by rest API. as this is just some defaulting and setting before the API.

Description

Specifically allowing profiles to be specified or defaulting back to environment variables.

I imagine a profile would have the same information as the call for PAT auth

  • token_name
  • personal_access_token
  • site_id
Dominant language
Python
Stars
716
Forks
446
Avg merge
8d 8h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tableau/server-client-python

All issues in tableau/server-client-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.