An example of a drupalpod.yaml file that could be included with a Contrib module.

example.drupalpod.yaml

# Each of these is a "profile" which can be enabled. Each profile is a set of 
# settings for your install that DrupalPod can configure for you. You MUST have
# at least a "default" key in this file, or it will be discarded entirely (default
# is the profile used if an alternative is not specified in the URL, in DP_EXTRA_SETTINGS).

default:
  # extra_packages: specifies additional composer packages to install. Use composer
  # constraint syntax
  extra_packages:
    - drupal/automatic_updates:^3
    - drupal/admin_toolbar
  
  # extra_packages_enable: which modules to enable after install. Specify them with
  # their namespace (this helps with things like drupal:ckeditor versus 
  # ckeditor:ckeditor from contrib)
  extra_packages_enable:
    - admin_toolbar:admin_toolbar
    - admin_toolbar:admin_toolbar_extra_tools
    - automatic_updates:package_manager
  
  # Run some additional drush commands at the end of install.
  extra_drush:
    - cr
  
  # Whether or not the repo is symlinked into the codebase. The default is true.
  # You may need to turn this off if you are have a known issue with symlinks
  # in your project. Note that the /repos/MODULE is the contrib codebase that
  # has a repo, and the version in web/ now must be updated using `composer install`
  symlink_repo: false
  
  # Only matters if symlink_repo is false. When this is the case, it will keep the
  # /repos/MODULE in sync with the web/ version using mutagen.
  sync_repo: true
  
developer:
  # Note that the developer profile does not imply the default profile. It
  # is completely separate. However, you can use [yaml anchors](https://medium.com/@kinghuang/docker-compose-anchors-aliases-extensions-a1e4105d70bd)
  # in order to write DRY yaml.
  extra_packages:
    - drupal/devel
    
  extra_packages_enable:
    - devel_generate

  extra_drush:
    - genc --types=page 50