(Migrated) enmasse problem

(This message has been automatically imported from the retired mailing list)

Hello,

There seems to be a typo issue with enmasse script for the amqp =
definitions:

I=E2=80=99m using this to export:

zato@aito:~/esb_services/config$ zato enmasse --input empty.json =
–export-local --export-odb /opt/zato_cluster/server1
Includes merged in successfully
ODB objects read
ODB objects merged in
Required elements missing
0 warnings and 1 error found:

±----------------±------------------------------------------------------=
-----------------------------------------------+
| Key | Value =
|

+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
| err0001/E08 | Missing key ‘service’ in ‘SeleniumAPIConsumer’, the =
rest is ‘{u’def_name’: u’RabbitMQ QA’, u’name’: |
| missing keys | u’SeleniumAPIConsumer’, u’service_name’: =
u’rabbitmq-selenium-api-consumer-service.screenshot- |
| | consumer’, u’is_active’: True, u’data_format’: =
u’json’, u’queue’: |
| | u’screenshots.service.selenium.results’, u’def_id’: =
1L, u’consumer_tag_prefix’: u’results’, u’id’: |
| | 1L}’ (channel_amqp) =
|

±----------------+=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94+

And this to import:

zato@chunli:~/esb_services/config$ zato enmasse --input qa_export.json =
–import /opt/zato_cluster/server1/
0 warnings and 1 error found:

±----------------±------------------------------------------------------=
-----------------------------------------------+
| Key | Value =
|

+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
| err0001/E11 | No service defined in ‘{u’def_name’: u’RabbitMQ QA’, =
u’name’: u’SeleniumAPIConsumer’, |
| service name | u’service_name’: =
u’rabbitmq-selenium-api-consumer-service.screenshot-consumer’, =
u’is_active’: True, |
| missing | u’data_format’: u’json’, u’queue’: =
u’screenshots.service.selenium.results’, u’def_id’: 1L, |
| | u’consumer_tag_prefix’: u’results’, u’id’: 1L}’ =
(channel_amqp) |

±----------------±------------------------------------------------------=
-----------------------------------------------+

It seems that the key =E2=80=98service=E2=80=99 should be =
=E2=80=98service_name=E2=80=99, in the documentation =
(https://zato.io/docs/admin/guide/enmasse.html?highlight=3Dchannel_amqp =
https://zato.io/docs/admin/guide/enmasse.html?highlight=3Dchannel_amqp) =
is =E2=80=98service=E2=80=99, but the generated son is =E2=80=98service_na=
me’=

On 11/03/15 19:12, Ivan Villareal wrote:

Hi Ivan,

There seems to be a typo issue with enmasse script for the amqp definitions:

I can confirm it - the attributes ‘service’ and ‘service_name’ can both
exist in input parameters to internal services but enmasse assumed it
would be always ‘service’ only.

This is dealt with in this commit …

… and will be released in 2.0.3 within 2 weeks.

thanks,