So it is the label attribute that is causing the failure in the DB layer. It took me a lot of hunting to find but I ended up getting:
$ juju exec --unit dummy-sink/0 "secret-add --label 'content-\u263a' --description 'my special secret' another-key=better"
secret://88d8febd-16bb-4374-8b01-cf48efe50575/cpbotlkefdci6ool96c0
creating secrets: Regular expression is invalid: PCRE does not support \L, \l, \N{name}, \U, or \u
I don't know what magic strings in the CSR could cause the "$regex" to fail, and arguably juju should be escaping the query it is supplying.
But we *also* should not be supporting arbitrary strings in our Label parameter.
So it is the label attribute that is causing the failure in the DB layer. It took me a lot of hunting to find but I ended up getting:
$ juju exec --unit dummy-sink/0 "secret-add --label 'content-\u263a' --description 'my special secret' another-key=better" //88d8febd- 16bb-4374- 8b01-cf48efe505 75/cpbotlkefdci 6ool96c0
secret:
creating secrets: Regular expression is invalid: PCRE does not support \L, \l, \N{name}, \U, or \u
I don't know what magic strings in the CSR could cause the "$regex" to fail, and arguably juju should be escaping the query it is supplying.
But we *also* should not be supporting arbitrary strings in our Label parameter.