I am trying to find what is the difference between the two terraform modules, google_bigquery_dataset_access and google_bigquery_dataset_iam, and I cannot seem to find clear information or maybe I am looking at it wrong. Both would give permissions on a dataset.
Could someone shed some light?
Thanks!
With the both you can set roles on Dataset for users. But
With google_bigquery_dataset_access you can define/grant authorized view
With google_bigquery_dataset_iam, you can define IAM and bindings in an idiomatic way and a more modern way
IMO, access is the legs of the BigQuery legacy version. If you can avoid to use it for IAM bindings, only for authorized view, it's better!
Related
I'm trying to automate a workflow using Google Data Studio. Requirements are simple - I need to be able to programatically copy a templated report (from a Python/Java application) and import/set a data source (Google Sheets doc) for that report. Nothing more fancy (no visualisation creation, formatting, or anything graphical, etc.).
Sources here, here and here (last two require Google Cloud Console account) suggest an API does exist (and detail a setup process to access it). However, after going through this setup process, I can find no details or documentation of any functionality, and consequently have been unable to progress.
Can anyone authoritatively state whether:
1. There does exist any API functionality for GDS? and
2. If not, are there plans to develop such? (since the Google links above suggest there is, I'm wondering if this means it's in the pipeline for near future).
The only directly related SO posts I can find are here and here. The first suggests there isn't, but doesn't account for the Google links I've provided above which suggest there is; the second doesn't really cover the same use case, so doesn't provide answers applicable here.
FYI - I've posted a Google Community forum post here asking essentially the same question.
If anyone is able to help out, that would be greatly appreciated :) Many thanks in advance for your time and help! :)
Fresh as of 2022-05-23
There does exist any API functionality for GDS?
Not in the way you are expecting. The three links you posted all refer to the current Data Studio API. The only things you can do with that API is view your Data Studio assets and update permissions. That's it. This API won't let you create/copy/modify reports or data sources.
If not, are there plans to develop such?
Not in the near future. You can make/vote for this feature request in the official tracker. More popular feature requests are usually prioritized in roadmaps.
That being said, a lot of the API use cases can be resolved using combinations of Community Connectors, config parameters, direct linking, viewer's credentials, Linking/Integration API etc.
Is there a way to see what role has been assigned to either local and remote (LDAP) users. For example, I want to see which users in an LDAP infrastructure have the nx-admin role assigned.
I've been looking via google and in the Nexus documentation, but haven't had much luck yet. I know I can check to see if a specific user has a role, but this isn't a scalable solution.
Thank you
There is no current way to do this. File an issue at: https://issues.sonatype.org/browse/NEXUS if you would, this sounds like a logical piece of functionality :)
Is there a convenient programatic way to create google plus test users?
I searched through most of the google plus apis provided in their dev resources portal, however did not find a decent way to create test users.
Any advice would be very helpful.
For general use, no there isn't a programmatic way to create test accounts.
However, if you have a Google Apps domain, you could use the Admin SDK to create user accounts within your domain, which would likely suffice for most testing that you might need to do. You'd also need to make sure that Google+ was enabled for the domain. And there are some limitations, such as not being able to use the plus.login scope.
I realize this solution is unlikely to work for most people, but you never know.
In GitHub for organizations is there a way to see how your org is doing on all of its milestones at once, as opposed to having to browse into each repo and click issues->milestones and only seeing that one?
If this is impossible from the interface I might go and set up an API-based solution if that's the only way.
I don't think it's possible from the interface, but it does look doable from the API.
You'll need to do a GET /user/repos and from the returned JSON Array do a GET /repos/:user/:repo/milestones on each repo.
As far as I know, the issue tracker is the same for both regular users and enterprise users. And regular users cannot browse all their issues in the same time.
So you probably need to play around with GitHub Issues API to get what you want.
DataHero does that! It can pull in all the issues across all repos for an organization.
We use DataHero internally to plot our progress on individual milestones, and across all milestones.
https://datahero.com/partners/github/
How we use it internally:
https://datahero.com/blog/2013/08/13/managing-github-projects-with-datahero/
Feel free to reach out if I can help in any way.
Disclosure: I work for DataHero
I'm working on setting up authentication with connect-auth on express & mongoose but there is just so much to do and it's kind of bogging me down. I could continue down this path but it seems like a lot like re-inventing the wheel.
EveryAuth (with MongooseAuth helper) looks rather appealing but the main reason I didn't go with it initially is that I have several account types with their own properties and workflows. For example, some account types require approval while others can login with oauth/openid without approval.
From looking over the examples, it looks like it is pretty opinionated over the general flow. I just don't know how difficult it would be or if it's even possible to step outside of the normal account auth approach.
Is it possible to have EveryAuth settings for each model type? If not, is there any other way to handle different workflows?
Thanks a lot!
You can customize findOrCreateUser in EveryAuth for each strategy ie: facebook, github