Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/support on demand access #26

Conversation

yair-develeap
Copy link

@yair-develeap yair-develeap commented Dec 2, 2024

Support OnDemandAccess --> see api: https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_users_and_groups.htm#create_group

Disable MinimumSiteRole requirement .. as it is optional .

tested locally using filesystem_mirror . and it works as it should .

@yair-develeap
Copy link
Author

Hi @GtheSheep any updates on this PR ?

@GtheSheep
Copy link
Owner

Hi @GtheSheep any updates on this PR ?

Will take a look this afternoon! thanks

@GtheSheep
Copy link
Owner

@yair-develeap seems reasonable! Thanks for putting this up! 🙌
Could you please:

  • Run make fmt to format
  • Run make doc to add the new flag to the site docs
  • Add a basic test case for this flag/ it's intended use into group_resource_test.go
    Thanks!

@yair-develeap
Copy link
Author

yair-develeap commented Dec 4, 2024

Hi @GtheSheep . done , including test cases .
ive also added a note for on_demand_access attribute . compatible from version 3.21 .

@GtheSheep
Copy link
Owner

Thanks!! Ran the tests locally, the on demand status doesn't seem to be getting set in the state correctly as it still appears in the plan after an apply.
If you don't have access to an instance to test this I can assist with the repo CI tomorrow, but it's likely a minor thing in how this can be true/ false/ nil or something 🤷🏻‍♂️

@yair-develeap
Copy link
Author

Your assistance would be greatly appreciated. Thank you!

@GtheSheep
Copy link
Owner

Hey @yair-develeap - apologies for the delay, hectic time of year! But it seems like there's something weird going on with this API on Tableau's side, the docs suggest the param is ephemeralUsersEnabled instead of externalUserEnabled, but trying that parameter causes the request to fail! Whilst externalUserEnabled seems to have no impact, and neither are returned in the response when GET'ing a group.
Have you had any luck applying this via the API in any format? If so could you possibly paste an example here please, I'm not super familiar with this setting so may just be my setup.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants