Asadmin recorder /FISH-69

[crazed-developer]

Description

---

My aim is to make my configuration through asadmin, instead of the admin interface. And what better way to generate the commands needed for that than to use the recorder.

Problem is that no command i have ever generated through the recorder has worked (Havent tried a lot though). Here i'll post a simple one:

The recorded action is to create a microprofile config property:

This creates these commands

asadmin> set property.payara\.microprofile\.k=v property.payara.microprofile.k.name=payara.microprofile.k
asadmin> set property.payara.microprofile.k.description=s

But when i issue them in the asadmin console, i get this error:

remote failure: No configuration found for property.payara.microprofile
Command set failed.

Expected Outcome

Upon further investigation (Payara documentation) i find that this is the correct command:

asadmin> set-config-property --propertyName=k --propertyValue=v --source=domain

Current Outcome

asadmin recorder generates the wrong commands

Steps to reproduce (Only for bug reports)

1. Download Payara 5.201
2. Fire: asadmin start-domain
3. Open console ./asadmin.sh
4. Fire the commands shown above.

Environment

• Payara Version: 5.201
• Edition: FULL
• JDK Version: OpenJDK 11
• Operating System: MAC

[rdebusscher]

Hi Steffen,

Thank you for the report of the issue with the MicroProfile config properties in combination with the asadmin recorder. I have created the internal issue CUSTCOM-215 to fix this in a future version.

Regards
Rudy

[lucguinchard]

Hello,

I have the same problem with asadmin recorder on a Payara Server 5.2020.7.
The asadmin recorder’s output is:

set resources.custom-resource.AM_Prod_Properties.property.log\.level=FINEST resources.custom-resource.AM_Prod_Properties.property.log.level.name=log.level
set resources.custom-resource.AM_Prod_Properties.property.log.level.description=

But I need a quad-backslash to make it work with asadmin:

set resources.custom-resource.AM_Prod_Properties.property.log\\\\.level=FINEST

I guess the fix hasn’t been merged yet. Could we hope a fix for the next release?

Thanks in advance.
Luc