#YAML Error: metadata attribute is required after correcting config.yml

1 messages · Page 1 of 1 (latest)

blissful burrowBOT
#

YAML Error: metadata attribute is required

If you are using PMM Nightly48 or above, this is expected behaviour.

metadata_path and overlay_path are now legacy attributes, and using them will cause the metadata attribute is required error

The error can be ignored as it won't cause any issues, or you can update your config.yml to use the new collection_files, overlay_files and metadata_files attributes as seen in the example from the wiki here:

libraries:
  Movies:
    collection_files:
      - pmm: imdb
    overlay_files:
      - pmm: resolution
    metadata_files:
      - file: config/metadata.yml
playlist_files:
  - pmm: playlists

https://metamanager.wiki/en/nightly/config/files/#example

mellow pastureBOT
#

📝 If you want to review this again, laryan61:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#

Welcome @vagrant seal!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

mellow pastureBOT
#

I recently switched to pmm nightly. Started getting the "YAML Error: metadata attribute is required" error in my logs. I updated my config.yml to replace the "_path" attributes with "_files" attributes as required. Doing so corrected most of the errors but still have several related to my external templates.yml file. I've attached the log, config and templates files for evaluations.

grim comet
#

what you have in metadate_files is not metadata

#

all that should go under collection_files

mellow pastureBOT
#

📝 If you want to review this again, bullmoose20:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

mellow pastureBOT
# mellow pasture
**Rec 03** - ❌ **METADATA ATTRIBUTE ERRORS**

METADATA ATTRIBUTE ERRORS
If you are using PMM nightly48 or newer, this is expected behaviour.
metadata_path and overlay_path are now legacy attributes, and using them will cause the YAML Error: metadata attribute is required error.
The error can be ignored as it won't cause any issues, or you can update your config.yml to use the new collection_files, overlay_files and metadata_files attributes.

The steps to take are:
:one: - Look at every file referred to within your config.yml and see what the first level indentation yaml file attributes are. They should be one of these(collections:, dynamic_collections:, overlays:, metadata:, playlists:, templates:, external_templates:) and can contain more than 1. For now, ignore the templates: and external_templates: attributes.
:two: - if it's metadata:, file it under the metadata_file: section of your config.yml
:three: - if it's collections: or dynamic_collections:, file it under the collection_files: section of your config.yml
:four: - if it's playlists:, file it under the playlist_files: section of your config.yml
:five: - if it's overlays:, file it under the overlay_files: section of your config.yml

*NOTE: If you only see templates: or external_templates:, this is a special case and you typically would not be referring to it directly in your config.yml file.

Within the attached log file, go to the indicated line(s) for more details on the exact issue and take actions to fix.
For more information on this, [https://metamanager.wiki/en/nightly/config/files/#example]
1 line(s) with METADATA ATTRIBUTE errors. Line number(s): 1800

mellow pastureBOT
arctic bronze
#

Rec 03 provides you with a systematic way of validating all your yml files.

#

And where to place them in your config.yml file

vagrant seal
arctic bronze