Is your feature request related to a problem? Please describe.
Marketplace metadata and package entries can be declared in apm.yml, but apm marketplace add cannot consume that configuration directly. Authors must first run apm pack --force to generate .github/plugin/marketplace.json, then register the generated file separately.
This creates an unnecessary two-step workflow during local development and can cause the generated manifest to become stale relative to apm.yml.
Describe the solution you'd like
Allow APM to load a marketplace declaration directly from an apm.yml file, for example:
apm marketplace add ./apm.yml --name example-marketplace
When the file contains a marketplace section, APM should resolve package sources relative to the apm.yml location and register the resulting marketplace without requiring a generated marketplace.json first. Existing workflows that consume a generated manifest or repository should continue to work unchanged.
APM should provide a clear validation error when the supplied apm.yml does not contain a usable marketplace declaration.
Describe alternatives you've considered
- Continue running
apm pack --force, then register ./.github/plugin/marketplace.json.
- Register a repository URL and rely on its generated marketplace manifest.
- Edit the generated
marketplace.json manually, which risks losing changes on the next build and conflicts with generated-file ownership.
Additional context
apm.yml is already the source configuration for marketplace metadata and package entries, while .github/plugin/marketplace.json is generated output. Direct loading would make the authoring source usable without weakening the generated-manifest workflow used for publishing and CI validation.
Is your feature request related to a problem? Please describe.
Marketplace metadata and package entries can be declared in
apm.yml, butapm marketplace addcannot consume that configuration directly. Authors must first runapm pack --forceto generate.github/plugin/marketplace.json, then register the generated file separately.This creates an unnecessary two-step workflow during local development and can cause the generated manifest to become stale relative to
apm.yml.Describe the solution you'd like
Allow APM to load a marketplace declaration directly from an
apm.ymlfile, for example:When the file contains a
marketplacesection, APM should resolve package sources relative to theapm.ymllocation and register the resulting marketplace without requiring a generatedmarketplace.jsonfirst. Existing workflows that consume a generated manifest or repository should continue to work unchanged.APM should provide a clear validation error when the supplied
apm.ymldoes not contain a usablemarketplacedeclaration.Describe alternatives you've considered
apm pack --force, then register./.github/plugin/marketplace.json.marketplace.jsonmanually, which risks losing changes on the next build and conflicts with generated-file ownership.Additional context
apm.ymlis already the source configuration for marketplace metadata and package entries, while.github/plugin/marketplace.jsonis generated output. Direct loading would make the authoring source usable without weakening the generated-manifest workflow used for publishing and CI validation.