Add application graph example with container, Redis cache, and volume

[Copilot]

Description

Adds a comprehensive test example demonstrating application graph visualization with interconnected resources: a Kubernetes container with an ephemeral volume connected to a Redis cache provisioned via Bicep recipe.

Changes

Application Definition (corerp-resources-container-redis-volume.bicep)

• Environment with corerp-redis-recipe from test registry
• Container with port 3000, readiness probe, ephemeral volume at /var/cache
• Redis cache extender with recipe-based provisioning
• Explicit connection from container to Redis

Test (Test_ApplicationGraphWithRedisAndVolume in application_test.go)

• Validates graph API returns container and Redis resources
• Verifies outbound/inbound connection between resources
• Confirms Kubernetes object generation (Deployments, Services, RBAC)

Documentation Package

• Architecture diagram and usage instructions
• Expected graph API response (JSON) and CLI output (text)
• Executable deployment script with step-by-step commands

Example

The Bicep template demonstrates recipe integration and graph relationships:

resource container 'Applications.Core/containers@2023-10-01-preview' = {
  properties: {
    container: {
      volumes: {
        cache: {
          kind: 'ephemeral'
          managedStore: 'disk'
          mountPath: '/var/cache'
        }
      }
    }
    connections: {
      redis: {
        source: redisCache.id  // Creates graph edge
      }
    }
  }
}

resource redisCache 'Applications.Core/extenders@2023-10-01-preview' = {
  properties: {
    recipe: {
      name: 'default'  // Uses corerp-redis-recipe
      parameters: { redisName: 'myredis' }
    }
  }
}

Graph visualization shows container → Redis connection with generated Kubernetes resources.

Type of change

• This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Contributor checklist

• An overview of proposed schema changes is included in a linked GitHub issue.
  • Yes
  • Not applicable
• A design document PR is created in the design-notes repository, if new APIs are being introduced.
  • Yes
  • Not applicable
• The design document has been reviewed and approved by Radius maintainers/approvers.
  • Yes
  • Not applicable
• A PR for the samples repository is created, if existing samples are affected by the changes in this PR.
  • Yes
  • Not applicable
• A PR for the documentation repository is created, if the changes in this PR affect the documentation or any user facing updates are made.
  • Yes
  • Not applicable
• A PR for the recipes repository is created, if existing recipes are affected by the changes in this PR.
  • Yes
  • Not applicable

Original prompt

look for recipes in the test directories then build an application definition that uses a kubernetes container, a redis cache and a volume. Then use that app definition to generate a visualization for the resulting application graph.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.