)]}'
{"releasenotes/notes/configdrive-support-in-anaconda-deploy-f2aad59b4ff809ec.yaml":[{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"f99bb18bc1b1a0c93f8a95d57e1245fea51ed016","unresolved":false,"context_lines":[{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The anaconda deploy interface now handles config drive. The config drive"},{"line_number":5,"context_line":"    contents are written to the disk in the /var/lib/cloud/seed/config_drive"},{"line_number":6,"context_line":"    directory by the driver via kickstart files %post section. cloud-init"},{"line_number":7,"context_line":"    picks up the the config drive information and processes them."},{"line_number":8,"context_line":"    Because the config drive is extracted on to disk as plain text files,"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"08acdcb5_62b7ded9","line":5,"updated":"2021-07-21 17:21:05.000000000","message":"ideally we should use double ticks for paths","commit_id":"f095a9478762a477b615b054f5623430c7c4a30f"}]}