On Superset (Airbnb/Apache) I'm trying to set the permission of the role "Financeiro" to the datasource "aleteia_contas" but it's missing. Superset version 0.17.1.
Related
i want to disabled acces for some user to some dashboards.
i enable DASHBOARD_RBAC feature flag in my config.py configuration file but i dont see the role filter appear in the edit propreties
DASHBOARD_RBAC = True
I'm using gcloud projects add-iam-policy-binding ... command to add role: roles/bigquery.jobs.create (because this is necessity if you want to be able to run query in BigQuery GCP project).
I get an output:
INVALID_ARGUMENT: Role roles/bigquery.jobs.create is not supported for this resource.
Problem here is I'm unable to set this through bq CLI as well, because it seems like permissions can be added on table/dataset level only. Anyone knows the possible solution (unix shell)?
The IAM role you mentioned in the question does not exist. It is a permission rather than a role.
The list of roles and their descriptions are provided in the BigQuery Predefined IAM roles
I am trying to create basic Composer environment:
image version: 1.17.8/2.1.4
using service account with composer.worker permission
my own user has project.owner permission
public ip
All my attempts failed with following error:
Http error status code: 400
Http error message: BAD REQUEST
Errors in: [Web server]; Error messages:
The caller does not have permission
Required 'deploymentmanager.typeProviders.create' permission for 'projects/<my-project>/global/typeProviders/europe-west2-<name-id>-addons-gke-typer'
deploymentmanager.typeProviders.create is covered by Deployment Manager Type Editor, so I added this permission to both my account and service account, but the error remains the same.
Cloud Composer Service Agent account is present in the project without any modifications to its permissions.
Is there anything else I can check or something that I missed during the set up?
For an account (whether User Account or Service Account) to be able to create a Composer Environment, the account must have a composer.environments.create permission.
And according to Google Cloud's documentation on Cloud Composer Access Control,
The Composer Worker role provides the permissions necessary to run a Cloud Composer environment
VM and intended for service accounts.
The Composer Worker role is not intended for creation of environments thus, it does not have the composer.environments.create permission.
If you want your service account to be able to create a Composer environment, you will need to assign the role Composer Administrator and this has the composer.environments.create permission needed.
You may refer to Access Control for Cloud Composer for the complete list of permission for Composer Worker, Composer Administrator and other Composer related roles.
TL;DR: Is it possible to use the AWS CLI to update the locally stored credentials file with the IAM users information in my AWS account?
I am following the instructions in this AWS Amplify tutorial which includes these steps:
Creating an IAM user
Providing the IAM user credentials to the amplify CLI
Step 2 updated my local \.aws\credentials file to include a profile for the IAM user created in step 1.
After this, of my own accord, I went back into the IAM console and created a new access key ID.
This new access key is not included in my local \.aws\credentials file, so I would like to add it. How can I do that?
I have tried copying the profile entry created by the amplify CLI tool and pasting in the aws_access_key_id and aws_secret_access_key. However, I am not sure how to update the toolkit_artifact_guid. As I am creating a new profile for the same IAM user, should I use the same toolkit_artifact_guid?
The aws configure command can be used to add a new profile to your config
Use the --profile flag to create a profile in the .aws/config file.
https://docs.aws.amazon.com/cli/latest/reference/configure/
toolkit-artifact-guid is a piece of metadata used by tooling, such as extensions for an IDE. It is not required for specifying a new IAM profile
Trying to use OS-login from my account, which has the owner role and compute os login admin role to connect to an instance with enable-oslogin TRUE. This used to work well (maybe a week or more ago), but lately it has been giving me this error.
This is within the same organization, same project. So not sure where the error is coming from.
Did GCP change their OS-Login feature? I am unable to find anything in the release notes.
gcloud compute ssh instance
ERROR: (gcloud.compute.ssh) User [user] does not have permission to access user [user:importSshPublicKey] (or it may not exist): Insufficient IAM permissions. The instance belongs to an external organization. You must be granted the roles/compute.osLoginExternalUser IAM role on the external organization to configure POSIX account information.
The GCP message is saying that you are running the gcloud tool with a credential that don’t belongs to the same organization from the project.
Try to run “gcloud auth list” to validate the authenticated user.
If the user is incorrectly select run the gcloud config command to change the logged user or gcloud auth login to log with the proper credentials.
I wish that this can help you,
Eduardo Ruela