Hey man how do you call APIs in python using "requests"
The user asks how to call APIs in Python using "requests". This is a general knowledge question, not a coding task in the repo necessarily. Let me give a concise, helpful answer. Ponytail governs what I build, not how I talk. This is a simple explanation question — answer directly and concisely.
Let me give a quick practical rundown.
Here's the practical core of it:
| locals { | |
| groups_files_path = "${local.source_directory}/groups" | |
| group_files = fileset("${local.groups_files_path}/", "*.yaml") | |
| all_groups = flatten([ | |
| for group_file in local.group_files : [ | |
| merge( | |
| yamldecode(file("${local.groups_files_path}/${group_file}")), |
| #!/usr/bin/env python3 | |
| """List/delete Harness IDP catalog entities that have a given | |
| metadata.integration_properties.<INTEGRATION> key (e.g. SonarQube). | |
| Usage: | |
| python3 idp_integration_cleanup.py SonarQube --list | |
| python3 idp_integration_cleanup.py SonarQube --delete # asks for confirmation | |
| python3 idp_integration_cleanup.py SonarQube --delete --yes # no prompt | |
| python3 idp_integration_cleanup.py SonarQube --step # confirm each entity individually | |
| python3 idp_integration_cleanup.py SonarQube --list --ignore HarnessCD,PagerDuty |
a harness delegate must be installed to enable containerized pipeline execution, access to internal resources, and deployments.
this requires a kubernetes cluster with outbound access to your harness account url: app.harness.io, app<cluster id>.harness.io, or <company name>.harness.io.
name the delegate something that relates to where it is deployed, cluster name is a good one.
| #!/usr/bin/env python3 | |
| """ | |
| Set a listener rule to send 100% of traffic to one target group and | |
| 0% to another target group. | |
| Fill in the three values below and run: python3 set_traffic_weight.py | |
| """ | |
| import boto3 |
| apiVersion: v1 | |
| kind: ServiceAccount | |
| metadata: | |
| name: argocd-manager | |
| namespace: kube-system | |
| --- | |
| apiVersion: v1 | |
| kind: Secret | |
| metadata: | |
| name: argocd-manager-token |
| apiVersion: harness.io/v1 | |
| kind: Workflow | |
| name: collecting data from api | |
| identifier: collecting_data_from_api | |
| type: test | |
| owner: snyder | |
| projectIdentifier: rssnyder | |
| orgIdentifier: default | |
| metadata: {} | |
| spec: |
| <+artifacts.primary.image>:<+artifacts.primary.tag> |
Harness Solutions Factory (HSF) is an automation framework that lets platform engineering teams define, publish, and govern reusable Harness resource bundles — and deliver them to developers through self-service, without requiring any Terraform or platform knowledge on the consumer side.
Platform admins author Terraform-backed templates that codify opinionated, repeatable configurations — things like a project pre-wired with environments, RBAC roles, user group bindings, pipelines, and connectors. These live in two places:
| ARG TOFU=1.11.6 | |
| FROM ghcr.io/opentofu/opentofu:$TOFU-minimal AS tofu | |
| FROM plugins/harness_terraform | |
| COPY --from=tofu /usr/local/bin/tofu /usr/local/bin/tofu |
