container-and-delivery

Automate Docker source packaging and delivery validation before merge.

36|7|Updated Jul 27, 2023

Search Tags:#checklist #containerization #docker #container #delivery #aci #events-md

Ready to run

npx skills add https://github.com/clemensv/real-time-sources --skill container-and-delivery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: container-and-delivery
Source: https://github.com/clemensv/real-time-sources/tree/main/.github/skills/container-and-delivery
Command: npx skills add https://github.com/clemensv/real-time-sources --skill container-and-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines packaging and delivery workflows for Docker-based sources ready for merge, ensuring all required documentation and deployment assets are prepared and validated.

Core Features & Use Cases

Dockerfile patterns: follow established docker layouts and ensure runtime packaging is container-ready.
Documentation contracts: generate and maintain CONTAINER.md and EVENTS.md to reflect deployment behavior.
Delivery assets: prepare azure-template.json, kql or fabric assets when needed, and ensure root catalog updates.
Validation: run the delivery validation checklist and Docker E2E tests before merge.

Quick Start

Run the delivery checklist to prepare a new source for merge, including updating Dockerfile, CONTAINER.md, EVENTS.md, and delivery assets.

Frequently Asked Questions about container-and-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prepare Docker sources for merge with containerization and delivery checklists?▼

To prepare Docker sources for merge, you must containerize the application with a Dockerfile, generate CONTAINER.md and EVENTS.md documentation, prepare delivery assets like azure-template.json, and validate everything using a repository-wide delivery checklist and end-to-end tests.

What documentation files are required for Docker container delivery?▼

Docker container delivery requires CONTAINER.md to describe deployment behavior and EVENTS.md to track events. These documentation contracts ensure the source is properly aligned and ready for merge alongside standard delivery assets.

How do I validate Docker-based sources before a merge?▼

You validate Docker-based sources by running a repository-wide delivery validation checklist and executing Docker end-to-end tests. This ensures the Dockerfile, documentation contracts, and delivery assets like azure-template.json are fully merge-ready.

Can I use Azure Container Instance templates for Docker container delivery?▼

Yes, Azure Container Instance templates are supported as delivery assets. You can prepare azure-template.json alongside Docker sources to facilitate deployment across Azure Container Instances, Fabric, or KQL assets.

What's the best way to package a Docker source for deployment across Azure and Fabric?▼

The best way to package a Docker source for Azure and Fabric deployment is to automate the workflow by ensuring a Dockerfile exists, generating CONTAINER.md and EVENTS.md, preparing azure-template.json or KQL assets, and validating with a delivery checklist.