Update patch set 3
Patch Set 3: (1 comment) Patch-set: 3
This commit is contained in:
parent
6624c78c4b
commit
42ffba0744
@ -129,6 +129,24 @@
|
||||
"revId": "4ede6253a130b488b9fdc5748133bccab8952e01",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
||||
"unresolved": false
|
||||
},
|
||||
{
|
||||
"key": {
|
||||
"uuid": "3f79a3b5_8dd63926",
|
||||
"filename": "specs/configurable-introspection-data-store.rst",
|
||||
"patchSetId": 3
|
||||
},
|
||||
"lineNbr": 122,
|
||||
"author": {
|
||||
"id": 10239
|
||||
},
|
||||
"writtenOn": "2018-09-28T13:25:12Z",
|
||||
"side": 1,
|
||||
"message": "The problem with throwing something in \"tools\" (for example) is that such things are usually not packaged (and thus not delivered to end users). But I\u0027m not talking about a DB migration in a strict sense, but rather about a new command of ironic-inspector-dbsync.\n\nWe could even create a completely new command (maybe that\u0027s what you meant - then sorry for confusion), something like ironic-inspector-data-migrate. As long as we ship it as a script installed in $PREFIX/bin (rather than just something in the tarball), it\u0027s fine.",
|
||||
"parentUuid": "3f79a3b5_0cb559d0",
|
||||
"revId": "4ede6253a130b488b9fdc5748133bccab8952e01",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
||||
"unresolved": false
|
||||
}
|
||||
]
|
||||
}
|
Loading…
Reference in New Issue
Block a user