fixed for the issue #1524

[vivekNEC]

fixed #1524

[AlvaroVega]

@vivekNEC Thanks for your great contribution.
I would like this PR should contain a tests (maybe a functional test) which raises the bug and then show how this PR is fixing the bug.
Maybe @Madhu-NEC could contribute it

[fgalan]

In addition to @AlvaroVega comment, please add an entry in CHANGES_NEXT_RELEASES describing the fix done by this PR. Suggestion:

- Fix: autoprovison now working with resources diferent from defaultResource (#1524)

[vivekNEC]

Hi @AlvaroVega is there any existing test cases related to service autoprovision that I could use as a reference. If there are any, could you please point me in the right direction?

[mapedraza]

Hi @AlvaroVega is there any existing test cases related to service autoprovision that I could use as a reference. If there are any, could you please point me in the right direction?

If you find in the repo you will find several examples like the following one:

iotagent-node-lib/test/unit/ngsiv2/ngsiService/active-devices-test.js

Line 904 in f7b914c

describe('When the IoT Agent receives autoprovisioned id and type measures', function () {

[AlvaroVega]

Hi @AlvaroVega is there any existing test cases related to service autoprovision that I could use as a reference. If there are any, could you please point me in the right direction?

I was thinking about something like

iotagent-node-lib/test/functional/testCases.js

Line 182 in f7b914c

describeName: '0020 - Simple group with active attributes',

[vivekNEC]

Hi @AlvaroVega
I checked all the functional tests you shared, but none seem related to that bug fix. Please let me know if I'm mistaken

[fgalan]

This was already included in https://github.com/telefonicaid/iotagent-node-lib/releases/tag/4.5.0 (I think it's here due to some mistake in github conflict resolution)

Suggested change

- Fix: default express limit to 1Mb instead default 100Kb and allow change it throught a conf env var 'IOTA_EXPRESS_LIMIT' (telefonicaid/iotagent-json#827)

[AlvaroVega]

Hi @AlvaroVega I checked all the functional tests you shared, but none seem related to that bug fix. Please let me know if I'm mistaken

There are other options to make tests as were described in: #1611 (comment)