ok, got it thanks for your support! On Mon, Jul 2, 2018 at 2:14 PM, Carlos Rodríguez <carlos.rodrig...@otrs.com> wrote:
> Hi Carlos, > > The idea for the —value is to be used for single string settings like > FQDN, if the setting requires a more complex data structure like Array, > Hash or any combination (e.g. HoA, AoH, AoA, HoH, HoAoH, AoHoA, then it > requires a YAML file. > > I understand that you would like to pass the YAML string into the —value, > to save time and do not crate an actual YAML file, but this is not > supported. > > > YAML its actually easy please take a look at the dictionary example at: > https://docs.ansible.com/ansible/latest/reference_ > appendices/YAMLSyntax.html > ((enjoy)) > > Carlos Rodríguez > > > > > On Jul 2, 2018, at 7:03 AM, carlos calvo <ccvillal...@gmail.com> wrote: > > Hi Carlos > > thanks for your answer. > > I am not aware of a specific syntax in YAML for hash. > Fact is, that if i try using a YAML file (using the source-path option) is > working > > [otrs@bss-otrs bin]$ ./otrs.Console.pl <http://otrs.console.pl/> > Admin::Config::Update --setting-name Ticket::Frontend:: > AgentTicketCompose###DynamicField --source-path ./example.yaml > > > Updating setting value... > > > Done. > > [otrs@bss-otrs bin]$ cat example.yaml > > AgentID: 1 > > > but i try to use the value directly, it isn't. I am sure it is a syntax > problem, but i tried YAML/PERL approaches to provide that parameter as a > hash and i keep getting this error. > > [otrs@bss-otrs bin]$ ./otrs.Console.pl <http://otrs.console.pl/> > Admin::Config::Update --setting-name Ticket::Frontend:: > AgentTicketCompose###DynamicField --value 'AgentID: 1' > > Updating setting value... > > > ERROR: OTRS-otrs.Console.pl-Admin::Config::Update-15 Perl: 5.16.3 OS: > linux Time: Mon Jul 2 13:53:29 2018 > > > Message: Setting Ticket::Frontend::AgentTicketCompose###DynamicField > Effective value is not correct: Its not a hash! > > > Traceback (25114): > > Module: Kernel::System::SysConfig::ConfigurationDeploy Line: 3483 > > Module: Kernel::System::Console::Command::Admin::Config::Update::Run > Line: 170 > > Module: (eval) Line: 461 > > Module: Kernel::System::Console::BaseCommand::Execute Line: 454 > > Module: Kernel::System::Console::InterfaceConsole::Run Line: 80 > > Module: ./otrs.Console.pl <http://otrs.console.pl/> Line: 38 > > > Error: Deployment failed! > > > > > > it would be great if you can provide an example using the "--value" option. > > Tx/Gracias! > Carlos. > > > > > On Sat, Jun 30, 2018 at 3:07 AM, Carlos Rodríguez < > carlos.rodrig...@otrs.com> wrote: > >> Hi Carlos, >> >> Sure, the answer is in the help >> >> [--source-path ...] - Specify the source location of the >> setting value YAML file. >> [--value ...] - Specify single line setting value. >> >> You need to set your hash as a YAML structure and put it into a file. >> >> ((enjoy)) >> >> Carlos Rodríguez >> >> >> >> >> On Jun 29, 2018, at 6:00 PM, carlos calvo <ccvillal...@gmail.com> wrote: >> >> Hi! >> >> i am running OTRS 6.0.8 and trying to setting things up over the console >> utility, otrs.Console.pl <http://otrs.console.pl/> >> I would like to configure a value in one of the parameters " >> Ticket::Frontend::AgentTicketCompose###DynamicField", >> but OTRS keeps complaining about the value type not being a hash. >> *Does anyone has an idea how to provide a hash value over this interface. >> I've tried several options but none did really worked out.* >> >> >>> [otrs@bss-otrs bin]$ perl ./otrs.Console.pl >>> <http://otrs.console.pl/> Admin::Config::Update --setting-name >>> Ticket::Frontend::AgentTicketCompose###DynamicField --value "(AgentID >>> => '1')" >>> Updating setting value... >>> ERROR: OTRS-otrs.Console.pl-Admin::Config::Update-15 Perl: 5.16.3 OS: >>> linux Time: Sat Jun 30 00:50:06 2018 >>> * Message: Setting Ticket::Frontend::AgentTicketCompose###DynamicField >>> Effective value is not correct: Its not a hash!* >>> Traceback (31978): >>> Module: Kernel::System::SysConfig::ConfigurationDeploy Line: 3483 >>> Module: Kernel::System::Console::Command::Admin::Config::Update::Run >>> Line: 170 >>> Module: (eval) Line: 461 >>> Module: Kernel::System::Console::BaseCommand::Execute Line: 454 >>> Module: Kernel::System::Console::InterfaceConsole::Run Line: 80 >>> Module: ./otrs.Console.pl <http://otrs.console.pl/> Line: 38 >>> Error: Deployment failed! >> >> >> >> >> Br&Tx >> Carlos. >> --------------------------------------------------------------------- >> OTRS mailing list: otrs - Webpage: http://otrs.org/ >> Archive: http://lists.otrs.org/pipermail/otrs >> To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs >> >> >> >> --------------------------------------------------------------------- >> OTRS mailing list: otrs - Webpage: http://otrs.org/ >> Archive: http://lists.otrs.org/pipermail/otrs >> To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs >> >> > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs > > > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs > >
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
