NAPPTIVE Playground CLI (playground-cli)

Create environments, deploy, and manage cloud-native apps without worrying about Kubernetes

Example Usage

This repository contains a collection of one Features - playground-cli. The sub-section below shows a sample devcontainer.json alongside example usage of the Feature.

playground-cli

Running playground-cli inside the built container.

"features": {
    "ghcr.io/oleksis/playground-cli/playground-cli:4": {}
}

$ playground --version

v4.3.0 [d28c04acdaca4966f52e5a483e500f28b86a1ae3]

Repo and Feature Structure

Similar to the devcontainers/features repo, this repository has a src folder. The Feature has its own sub-folder, containing at least a devcontainer-feature.json and an entrypoint script install.sh.

├── src
│   ├── playground-cli
│   │   ├── devcontainer-feature.json
│   │   └── install.sh
|   ├── ...
│   │   ├── devcontainer-feature.json
│   │   └── install.sh
...

An implementing tool will composite the documented dev container properties from the feature's devcontainer-feature.json file, and execute in the install.sh entrypoint script in the container during build time. Implementing tools are also free to process attributes under the customizations property as desired.

Options

All available options for a Feature should be declared in the devcontainer-feature.json. The syntax for the options property can be found in the devcontainer Feature json properties reference.

For example, the playground-cli feature provides an proposals of two possible options (latest, 4.3.0). If no option is provided in a user's devcontainer.json, the value is set to "4.3.0".

{
    // ...
    "options": {
        "version": {
            "type": "string",
            "proposals": [
                "latest",
                "4.3.0"
            ],
            "default": "4.3.0",
            "description": "Select or enter a NAPPTIVE Playground CLI version"
        }
    }
}

Options are exported as Feature-scoped environment variables. The option name is captialized and sanitized according to option resolution.

#!/bin/sh
set -e

PLAYGROUND_VERSION=${VERSION}
echo "Activating feature 'playground-cli' version v${VERSION}"

...

Distributing Features

Versioning

Features are individually versioned by the version attribute in a Feature's devcontainer-feature.json. Features are versioned according to the semver specification. More details can be found in the dev container Feature specification.

Publishing

NOTE: The Distribution spec can be found here.

While any registry implementing the OCI Distribution spec can be used, this template will leverage GHCR (GitHub Container Registry) as the backing registry.

Features are meant to be easily sharable units of dev container configuration and installation code.

This repo contains a GitHub Action workflow that will publish each feature to GHCR. By default, each Feature will be prefixed with the <owner/<repo> namespace. For example, the two Features in this repository can be referenced in a devcontainer.json with:

ghcr.io/oleksis/playground-cli/playground-cli:4

The provided GitHub Action will also publish a third "metadata" package with just the namespace, eg: ghcr.io/oleksis/playground-cli/. This contains information useful for tools aiding in Feature discovery.

'oleksis/playground-cli/' is known as the feature collection namespace.

Marking Feature Public

Note that by default, GHCR packages are marked as private. To stay within the free tier, Features need to be marked as public.

This can be done by navigating to the Feature's "package settings" page in GHCR, and setting the visibility to 'public`. The URL may look something like:

https://github.com/users/<owner>/packages/container/<repo>%2F<featureName>/settings

Adding Features to the Index

If you'd like your Features to appear in our public index so that other community members can find them, you can do the following:

• Go to github.com/devcontainers/devcontainers.github.io
  • This is the GitHub repo backing the containers.dev spec site
• Open a PR to modify the collection-index.yml file

This index is from where supporting tools like VS Code Dev Containers and GitHub Codespaces surface Features for their dev container creation UI.

Using private Features in Codespaces

For any Features hosted in GHCR that are kept private, the GITHUB_TOKEN access token in your environment will need to have package:read and contents:read for the associated repository.

Many implementing tools use a broadly scoped access token and will work automatically. GitHub Codespaces uses repo-scoped tokens, and therefore you'll need to add the permissions in devcontainer.json

An example devcontainer.json can be found below.

{
    "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
    "features": {
     "ghcr.io/oleksis/playground-cli/playground-cli:4": {
            "version": "4.3.0"
        }
    },
    "customizations": {
        "codespaces": {
            "repositories": {
                "my-org/private-features": {
                    "permissions": {
                        "packages": "read",
                        "contents": "read"
                    }
                }
            }
        }
    }
}