Google Cloud Platform Friendly Pilot
Project description
Google Cloud Pilot
Installation
pip install gcp-pilot
Some APIs need extra packages, thus you must use extras to add them:
- Cloud Tasks:
pip install gcp-pilot[tasks] - Cloud Build:
pip install gcp-pilot[build] - Cloud Storage:
pip install gcp-pilot[storage] - Big Query:
pip install gcp-pilot[bigquery] - Speech:
pip install gcp-pilot[speech] - Sheets:
pip install gcp-pilot[sheets] - Pub/Sub:
pip install gcp-pilot[pubsub] - Datastore:
pip install gcp-pilot[datastore] - Cloud DNS:
pip install gcp-pilot[dns] - Secret Manager:
pip install gcp-pilot[secret] - Healthcare Engine:
pip install gcp-pilot[healthcare] - IAM:
pip install gcp-pilot[iam]
Usage
from gcp_pilot.resource import ResourceManager
grm = ResourceManager()
Default Values
Credentials
gcp-pilot uses ADC to detect credentials. This means that you must have one of the following setups:
- Environment variable
GOOGLE_APPLICATION_CREDENTIALSpointing to the JSON file with the credentials - Run inside GCP (Compute Engine, Cloud Run, GKE, AppEngine), so the machine's credentials will be used
You can also globally set a service account using the environment variable DEFAULT_SERVICE_ACCOUNT, which will require impersonation.
Project
When creating a client, a default project is defined by using the project that the credentials belongs to.
Clients that support managing resources from other projects can be overwritten per call.
Example: you create a
BigQueryclient using credentials fromproject_a. All calls will query datasets fromproject_a, unless another project is passed as parameter when performing the call.
You can also globally set a project using the environment variable DEFAULT_PROJECT
Location
Very similar to default project, a default location is defined by using the project's location. The project's location will exist if you ever enabled AppEngine, so you had to set a location then. Otherwise, no default location will be set.
You can also globally set a location using the environment variable DEFAULT_LOCATION and reduce the amount of API calls
when creating clients.
Why Use gcp-pilot
"Since Google already has a generic API client and so many specific clients, why should I use this library?"
Google's has 2 types of clients:
- dedicated: custom-made for the APIs. They are excellent: they implement high level interaction with the API with friendly methods. The
gcp-pilotcan adds its value by handling authentication, friendly errors and parameter fallback. - generic: a single client that is capable of dynamically calling any REST API. They are a pain to use: very specific calls that must be translated from the documentation. The
gcp-pilotcomes in handy to add high-level interaction with friendly method such asCalendar.create_event, on top of all other vantages cited above.
Parameter Fallback
Most API endpoints require project_id (sometimes even project_number) and location.
So gcp-pilot automatically detects these values for you, based on your credentials (although it'll require extra permissions and API calls).
If you use multiple projects, and your credentials is accessing other projects, you can still customize the parameters on each call to avoid the default fallback.
Friendly Errors
Most APIs return a generic HttpException with am embedded payload with error output, and also there's a couple of different structures for these payloads.
So gcp-pilot tries its best to convert these exceptions into more friendly ones, such as NotFound, AlreadyExists and NotAllowed.
It'll be much easier to capture these exceptions and handle them by its type.
Identification Features
- Authentication: each client uses ADC, which consists on trying to detect the service account with fallbacks: SDK > Environment Variable > Metadata
- Impersonation: it's possible to create clients with
impersonate_accountparameter that impersonates another account. - Delegation: services (eg. Google Workspace) that requires specific subjects are automatically delegated, sometimes even performing additional credential signatures.
- Region: most GCP services requires a location to work on (some even require specific locations). If not provided, the clients use the project's default location, as defined by App Engine.
- Authorization: OIDC authorization is automatically generated for services (eg. CloudRun) that require authentication to be used.
Auto-Authorization
Some services require specific authorizations that should be setup prior to its usage, some examples:
- [Pub/Sub] subscribe to a topic with authenticated push;
- [Cloud Scheduler] schedule a job to trigger a Cloud Run service;
- [Cloud Tasks] queue a task to trigger a Cloud Run service;
In these cases, gcp-pilot tries its best to assure that the required permissions are properly set up
before the actual request is made.
Integration
Some services can be integrated, and gcp-pilot does just that in a seamless way by adding helper methods.
Example: you can subscribe to Google Cloud Build's events to be notified by every build step.
By using CloudBuild.subscribe, the gcp-pilot creates a subscription (and the topic, if needed) in the Google Pub/Sub service.
Supported APIs
- IAM
- manage service accounts
- manage permissions
- encode & decode JWT tokens
- Identity Platform
- sign in users
- sign up users
- reset password flow
- verify email flow
- Credentials
- manage API Keys
- Resource Manager
- manage projects
- manage permissions
- Secret Manager
- manage secrets
- Identity Aware Proxy
- generate OIDC token
- Source Repositories
- manage repositories
- Directory:
- manage users
- manage groups
- People:
- get people
- Cloud SQL
- manage instances
- manage databases
- manage users
- Cloud Storage
- manage buckets
- manage files
- Cloud Build
- manage triggers
- Cloud Functions
- manager functions
- manage permissions
- Cloud Scheduler
- manage schedules
- Cloud Tasks
- manage tasks & queues
- Cloud Run
- read services
- manage domain mappings [1]
- API Gateway
- manage APIs
- manage API Configs
- manage Gateways
- Service Usage
- enable/disable APIs and Services
- BigQuery
- manage datasets
- perform queries
- Calendar
- manage events
- Google Chats
- build complex messages
- call webhook
- interact as bot
- Cloud Directory
- manage groups
- Cloud DNS
- manage DNS zones
- manage zone's registers
- Sheets
- manage spreadsheets (powered by gspread)
- Speech
- recognize speech from audio
- Datastore
- Object Mapping ("ORM-ish" management of documents)
- Monitoring
- reporting errors
- logging
- manage custom services
- Healthcare
- Manage datasets
- Manage stores
- Manage FHIR resources: powered by fhir-resources
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file gcp_pilot-1.7.0.tar.gz.
File metadata
- Download URL: gcp_pilot-1.7.0.tar.gz
- Upload date:
- Size: 56.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: poetry/1.3.2 CPython/3.11.1 Linux/5.15.0-1031-azure
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 299577ab93489cdd1f4760d5b76febf13f8efff5783bd1109e3b38b8b58408e9 |
|
| MD5 | e06b23ce276b715b8cb606f7fda9c23e |
|
| BLAKE2b-256 | 0c50eb0ce2c7f0a2e4850167191c30a25484d864627fb44290df5b793b717924 |
File details
Details for the file gcp_pilot-1.7.0-py3-none-any.whl.
File metadata
- Download URL: gcp_pilot-1.7.0-py3-none-any.whl
- Upload date:
- Size: 68.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: poetry/1.3.2 CPython/3.11.1 Linux/5.15.0-1031-azure
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | ca3c514be663064fecf0a20f682f14239d81ed60973c43bb30d9ef75705569ac |
|
| MD5 | 0adca96c106f32897e01b125b58413d4 |
|
| BLAKE2b-256 | fd46bd7a86e02055af8206dbadeb6f805083faba86754bf7410422ba7876cd71 |
