openstack
/
charm-glance
Code Issues Proposed changes

Update patch set 2 

Patch Set 2:

(1 comment)

Patch-set: 2
CC: Gerrit User 20870 <20870@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
This commit is contained in:
Gerrit User 20870 2024-04-05 17:16:54 +00:00 committed by Gerrit Code Review
parent c903256613
commit a88b1ea04c
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
07da644b2ba6a2371cf7ef5249e196f18a3b8823
View File

@ -17,6 +17,23 @@
"revId": "07da644b2ba6a2371cf7ef5249e196f18a3b8823",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": false,
"key": {
"uuid": "76bc4809_0a23fb1d",
"filename": "/PATCHSET_LEVEL",
"patchSetId": 2
},
"lineNbr": 0,
"author": {
"id": 20870
},
"writtenOn": "2024-04-05T17:16:54Z",
"side": 1,
"message": "Can I just verify my understanding. The new key/value pairs will be placed into glance-api.conf via the `enabled_backend_configs` key? e.g. in\n\n {% for name, cfg in enabled_backend_configs.items() %}\n [{{name}}]\n {% for key, val in cfg.items() -%}\n {{ key }} \u003d {{ val }}\n {% endfor -%}\n {% endfor%}\n \nin the template? I was a bit confused as there were no template changes, but I think it happens automatically. Unfortunately, there\u0027s no unit test to verify that it\u0027s happening, which I think would be very useful.",
"revId": "07da644b2ba6a2371cf7ef5249e196f18a3b8823",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {