v4 VS cli

import concurrent import boto3 import os import requests import mimetypes from botocore.exceptions import NoCredentialsError S3_ACCESS_KEY = os.getenv('S3_ACCESS_KEY') S3_SECRET_KEY = os.getenv('S3_SECRET_KEY') S3_BUCKET = os.getenv('S3_BUCKET') S3_ENDPOINT = os.getenv('S3_ENDPOINT') CI_PROJECT_ID = os.getenv('CI_PROJECT_ID') CI_MERGE_REQUEST_IID = os.getenv('CI_MERGE_REQUEST_IID') GITLAB_TOKEN = os.getenv('GITLAB_TOKEN') COVERAGE_REPORT_FOLDER = os.getenv('COVERAGE_REPORT_FOLDER') CI_PIPELINE_IID = os.getenv('CI_PIPELINE_IID') CI_PROJECT_NAME = os.getenv('CI_PROJECT_NAME') S3_REGION = os.getenv('S3_REGION') s3_client = boto3.client('s3', aws_access_key_id=S3_ACCESS_KEY, aws_secret_access_key=S3_SECRET_KEY) def upload_file(bucket_name, dir_path, file_path, prefix, s3_client): relative_path = os.path.relpath(file_path, dir_path) bucket_key = f'{prefix}/{relative_path}'.replace('\\', '/') mime_type = mimetypes.guess_type(file_path)[0] if mimetypes.guess_type(file_path)[0] else 'application/html' extra_args = {'ContentType': mime_type, 'StorageClass': 'STANDARD'} try: s3_client.upload_file(file_path, bucket_name, bucket_key, extra_args) print(f'Uploaded file {file_path} as {mime_type}') except Exception as e: print(f'Failed to upload file {file_path} to bucket {bucket_name}/{bucket_key}: {str(e)}') def upload_dir(bucket_name, dir_path, prefix): with concurrent.futures.ThreadPoolExecutor() as executor: for root, dirs, files in os.walk(dir_path): for file in files: file_path = os.path.join(root, file) try: executor.submit(upload_file, bucket_name, dir_path, file_path, prefix, s3_client) except Exception as e: print(f'error: {e}') def add_merge_request_comment(gitlab_token, project_id, merge_request_iid, message): print('Creating a new merge request comment...') url = f'https://gitlab.com/api/v4/projects/{project_id}/merge_requests/{merge_request_iid}/notes' headers = {'Content-Type': 'application/json', 'Private-Token': gitlab_token} data = {'body': message} try: response = requests.post(url, headers=headers, json=data) response.raise_for_status() print(f'Merge request updated with coverage report access link.') except requests.exceptions.HTTPError as err: print(f'Failed to add a merge request comment: {err}') if __name__ == '__main__': pipeline_slug = f'coverage/{CI_PROJECT_NAME}-{CI_PIPELINE_IID}' try: upload_dir(S3_BUCKET, COVERAGE_REPORT_FOLDER, pipeline_slug) print('All files uploaded successfully.') access_url = f'https://s3.{S3_REGION}.amazonaws.com/{S3_BUCKET}/{pipeline_slug}/index.html' message = f'The coverage report is ready. Check it out [here]({access_url})!' print(message) add_merge_request_comment(GITLAB_TOKEN, CI_PROJECT_ID, CI_MERGE_REQUEST_IID, message) except NoCredentialsError: print('No s3 credentials found.') except Exception as e: print('Error:', e)

#!/bin/bash # list-tags.sh # List all Gitlab tags for a given project. # $CI_PROJECT_ID is a Gitlab pre-defined variable # $GITLAB_TOKEN is a project access token that needs to be # a defined CI/CD variable. GITLAB_API_URL="https://gitlab.com/api/v4/projects/${CI_PROJECT_ID}" curl -k --header "PRIVATE-TOKEN: $GITLAB_TOKEN" "${GITLAB_API_URL}/repository/tags"

# ~/.npmrc @doppelmutzi:registry=https://gitlab.com/api/v4/projects//packages/npm/ //gitlab.com/api/v4/projects//packages/npm/:_authToken=

GITLAB_API_URL = "https://gitlab.com/api/v4" PRIVATE_TOKEN = "" NAMESPACE = "mycompany" PROJECT_NAME = "test-project"

import requests app = FastAPI() # GitLab API configuration GITLAB_API_URL = "https://gitlab.com/api/v4" PRIVATE_TOKEN = "" PROJECT_ID = "vinod827_1391/awesome" def grant_developer_access(username: str): # Get user details from GitLab user_url = f"{GITLAB_API_URL}/users?username={username}" response = requests.get(user_url, headers={"PRIVATE-TOKEN": PRIVATE_TOKEN}) user_data = response.json() if not user_data: raise HTTPException(status_code=404, detail=f"User {username} not found.") user_id = user_data[0]["id"] # Grant developer access to the project access_data = {"user_id": user_id, "access_level": 30} # 30 is the access level for developer access_url = f"{GITLAB_API_URL}/projects/{PROJECT_ID}/access_requests" response = requests.post(access_url, headers={"PRIVATE-TOKEN": PRIVATE_TOKEN}, json=access_data) print('response->', response) if response.status_code != 201: raise HTTPException(status_code=response.status_code, detail=response.text)

Invoke-RestMethod -Uri "https://gitlab.com/api/v4/projects/12345/repository/tags" -Headers $headers -Method POST -Body $jsonBody

Hello everyone i'm trying to install Librewolf on my M1 MBA running fedora39 with gnome on wayland, I downloaded librewolf's compressed archive from https://gitlab.com/api/v4/projects/44042130/packages/generic/librewolf/120.0.1-1/librewolf-120.0.1-1-linux-arm64-package.tar.bz2

repositories { maven { url "https://gitlab.com/api/v4/projects/PROJEC-ID/packages/maven" credentials(HttpHeaderCredentials) { name = "Private-Token" value = gitLabPrivateToken } authentication { header(HttpHeaderAuthentication) } } } }

Pagina da Gitlab: https://gitlab.com/api/v4/projects/44042130/packages/generic/librewolf/116.0-1/librewolf-116.0-1-windows-x86_64-setup.exe

.base: image: alpine:3.18 before_script: - echo "Project is $CI_PROJECT_NAME" script: - apk update - apk --no-cache add git openssl ca-certificates curl perl https://$GITLAB_USER_NAME:$SVC_ACCESS_TOKEN@$CI_SERVER_HOST/$CI_PROJECT_PATH.git - mkdir -p /usr/local/share/ca-certificates/extra - openssl s_client -connect ${CI_SERVER_HOST}:${CI_SERVER_PORT} -servername ${CI_SERVER_HOST} -showcerts /dev/null | sed -e '/-----BEGIN/,/-----END/!d' | tee "/usr/local/share/ca-certificates/${CI_SERVER_HOST}.crt" >/dev/null - update-ca-certificates - curl --location --output /usr/local/bin/release-cli "https://gitlab.com/api/v4/projects/gitlab-org%2Frelease-cli/packages/generic/release-cli/latest/release-cli-linux-amd64" - chmod +x /usr/local/bin/release-cli - release-cli -v Versioning: stage: Version extends: - .base script: - if [[ "$CI_COMMIT_BRANCH" == *"feature/"* ]]; then IMAGE_TAG="nightly" ; elif [ "$CI_COMMIT_BRANCH" == "develop" ]; then IMAGE_TAG="devel"; else echo "Master/Main branch"; fi - echo "Version found is ${IMAGE_TAG}" allow_failure: false rules: - if: '$CI_COMMIT_BRANCH =~ /^(develop|main|feature.*$)$/' artifacts: paths: - $IMAGE_TAG expire_in: 1 minute

GitHub CLI - GitHub on the command line. Great for creating PRs, etc.

This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.

You might be interested in GitHub's cli tool, which is open source, if you want to access GitHub without running their proprietary JS code.

https://cli.github.com/

👉 Note: This script uses the GitHub CLI. So make sure you've installed that if you haven't already. Instructions here.

View on GitHub

(Context: I'm pretty thick into Nix, and have been for about four years. Most of this post is focussed on the NixOS desktop experience, so DevOps nerds, ymmv.)

Unpopular opinion: Nix is not that hard.

What's "hard" from a nix-promotion strategy is motivating people to understand why they would want the benefits it offers. Mostly because Nix, especially with home-manager, dramatically worsens UX for several day-to-day tasks, simply by violating the Law of Least Surprise every couple of hours in normal use.

I want a fully idempotent, version-locked, rewindable user environment, with a version-controlled central config, because I have half a dozen devices that, for reasons, I need to keep perfectly interchangeable with one another. Most users do not want this, for the simple fact that mutating their configs and differentiating them locally on specific machines is not a bug, but a feature.

Even more than that, it's an expectation that most software developers share as well.

Case in point: I filed a bug against the GitHub CLI last week. If any org has the scope and motivation to build software that's compatible with NixOS, an OS most of whose users are developers, it should be GitHub, which is, at least notionally, all about developers, developers, developers. A change in GH required a config format migration, which was sensibly done by opening the config .yml and rewriting it.

Of course, this breaks NixOS not just in practice but in principle. NixOS/home-manager makes config files read-only. Surprise! https://github.com/cli/cli/issues/8462

The response from GitHub was basically, "yeah, we knew this was going to happen, we mentioned it to the packagers at NixOS, but we did it anyway, because it was still the best way to proceed for us." (And they weren't wrong.)

Now, once a month is an annoyance, but I run into these problems daily. I can't imagine any sane person -- which I am not -- would persist with using it.

Why do I keep using NixOS, then? Because I am terribly and disproprotionately annoyed by small changes in my user experience, which I find disruptive to my workflow and hence threaten my success. For me, forbidding apps from mutating the config files I established for them is a selling point. Being able to version-control an idempotent declarative config for all of them at once is heaven.

Unless you're like me, you'll hate NixOS. But some were meant for Nix.

Because

To use a proper dynamic auth for ghcr.io you can create a "credential helper" and then it is supported by flux, see here: https://fluxcd.io/flux/cheatsheets/oci-artifacts/#authentication Unfortunately the "official" credential helper for ghcr.io doesn't exist. I use this simple script as a helper: https://gist.github.com/pkit/a98411d21ecc9293066f4579088187d1 Which requires gh cli to be installed.

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.

Two CLI tools I install right away are the GitHub CLI (via brew) and the Netlify CLI (via npm).