vmactions/omnios-vm c6dc510aedb32975a790786ce30904003c7b367b
“Test your code in a real OmniOS virtual machine on GitHub Actions -- QEMU-powered, with SSH and two-way folder sync”
AArch64 (ARM64) architecture stringAction declares a main entrypoint
SHA-2564e75f43748b25b404a335ad3cdffc592f3a4a58da95110cd22135e81c77fb269
Evidence
⋯7 lines
8 ls -lah
9 whoami
10 env
11 psrinfo -vp
12 cat /etc/release
13 psrinfo -v
14 echo "::memstat" | mdb -k
15 echo "OK"
1# Run GitHub CI in {{VM_NAME}}
2
3
4
5
6
7See all the supported VMs: [VMActions.org](https://vmactions.org)
8
9Powered by [AnyVM.org](https://anyvm.org)
10
11## :robot: AI Ready
12
13> [!TIP]
14> **You don't need to write this workflow by hand.**
15>
16> These VMs are now AI-ready. With the **[vmactions-ci skill](https://github.com/vmactions/vmactions-skill)**, an AI coding agent -- Claude Code, Codex, Copilot CLI, Gemini CLI, and others -- understands the full vmactions interface and writes the GitHub Actions CI for you, **automatically**.
17>
18> Just describe what you want in plain language, e.g. *"run my tests on {{VM_NAME}}"* or *"check that my project builds on {{VM_NAME}} aarch64"*, and the agent generates a correct, ready-to-commit `test.yml`. It will:
19>
20> - pick the right action, `release`, an …
⋯8 lines
40
41
42## 1. Example: `test.yml`:
43
44```yml
45
46name: Test
47
48on: [push]
49
50jobs:
⋯5 lines
1"use strict";
2// Copyright (c) Microsoft Corporation.
3// Licensed under the MIT license.
4Object.defineProperty(exports, "__esModule", { value: true });
5exports.AbortError = void 0;
6var AbortError_js_1 = require("./AbortError.js");
7Object.defineProperty(exports, "AbortError", { enumerable: true, get: function () { return AbortError_js_1.AbortError; } });
8//# sourceMappingURL=index.js.map
1import type { AuthorizeRequestOnChallengeOptions } from "@azure/core-rest-pipeline";
2/**
3 * Converts: `Bearer a="b", c="d", Bearer d="e", f="g"`.
4 * Into: `[ { a: 'b', c: 'd' }, { d: 'e', f: 'g' } ]`.
5 *
6 * @internal
7 */
8export declare function parseCAEChallenge(challenges: string): any[];
9/**
10 * CAE Challenge structure
11 */
12export interface CAEChallenge {
13 scope: string;
14 claims: string;
15}
16/**
17 * This function can be used as a callback for the `bearerTokenAuthenticationPolicy` of `@azure/core-rest-pipeline`, to support CAE challenges:
18 * [Continuous Access Evaluation](https://learn.microsoft.com/azure/active-directory/conditional-access/concept-continuous-access-evaluation).
19 *
20 * Call the `bearerTokenAuthenticationPolicy` with the following options:
21 *
22 * ```ts snippet:AuthorizeRequestOnClaimChallenge
23 * import { bearerTokenAuthenticationPolicy } from "@azure/core-rest-pipeline";
24 * import { authorizeRequestOnClaimChallenge } from "@azure/core-client";
25 *
26 * const policy = bearerTokenAuthenticationPolicy({
27 * challengeCallbacks: {
28 * authorizeRequestOnChallenge: authorizeRequestOnClaimChallenge,
29 * },
30 * scopes: ["https://service/.default"],
31 * });
32 * ```
33 *
34 * Once provided, the `bearerTokenAuthenticationPolicy` policy will internally handle Continuous Access Evaluation (CAE) challenges.
35 * When it can't complete a challenge it will return the 401 (unauthorized) response from ARM.
36 *
37 * Example challenge with claims:
38 *
39 * ```
40 * Bearer authorization_uri="https://login.windows-ppe.net/", error="invalid_token",
41 * error_description="User session has been revoked",
42 * claims="eyJhY2Nlc3NfdG9rZW4iOnsibmJmIjp7ImVzc2VudGlhbCI6dHJ1ZSwgInZhbHVlIjoiMTYwMzc0MjgwMCJ9fX0="
43 * ```
44 */
45export declare function authorizeRequestOnClaimChallenge(onChallengeOptions: AuthorizeRequestOnChallengeOptions): Promise<boolean>;
46//# sourceMappingURL=authorizeRequestOnClaimChallenge.d.ts.map
Showing the top 5 files — 8 more files (33 regions) not shown.
No evidence locations were recorded for this file. Raw result