Skip to content

Understanding Feeds

A Feed in VDC is a logical container for managing ingredients and their releases within a specific project. Feeds define the scope of visibility, packages storage, and naming context for all ingredients under them.

Each feed:

  • Belongs to a single project
  • Contains multiple ingredients
  • Has a qualified name: project.feed
  • Defines the Azure Blob container where release packages are stored
  • Controls version isolation and namespace per ingredient

Feeds provide organizational boundaries that help teams manage ingredients independently while reusing the same ingredient names across different contexts.

Relationship Between Project, Feed, and Ingredient

[Project: validation-team]
   ├── [Feed: main]
   │     └── [Ingredient: acode]
   │             └── [Releases...]
   └── [Feed: experimental]
         └── [Ingredient: acode]
                 └── [Releases...]

Feed Naming and Qualified Identity

  • Feed names must be unique within a project
  • A fully qualified ingredient name is: project.feed.ingredient
  • The same ingredient name can exist in:
    • Different feeds (e.g., main.acode_ptl vs. experimental.acode_ptl)
    • Different projects entirely

Artifact Storage and Isolation

  • Each feed has a dedicated Azure Blob container for storing artifacts
  • Every release within a feed stores its files in a separate folder inside that container
  • Storage is fully isolated between feeds and environments (e.g., Dev, Test, Production)

%%TODO: verify that this is correct and add the information about the antifactory%%

Feed Metadata and Retention

  • Feed metadata is stored in Azure CosmosDB
  • There is no enforced retention policy yet — ingredients and releases are stored indefinitely unless manually deleted
  • In future, VDC may support user-defined retention per feed

Permissions and Access

  • Feeds inherit access control from the project they belong to
  • All ingredient creation and release submission is scoped by feed-level permissions
  • Users can only create or edit ingredients in feeds they have access to

Common Use Cases

%%TODO: add use cases that we recommend for how to define projects%%