CODEWITHSUNDEEP
ibm-cloudiot
Ketu
Ketu

Reputation: 1718

MQTT settings not getting reflected if they are changed after deploying the code on Bluemix

I created an app under IoT on Bluemix. I added a key and an auth token under the MQTT settings and then deployed the application. Now due to some reason I changed the access key, updated the key and token in the MQTT settings, and delivered the code. However, the new key isn't reflected in the VCAP_SERVICES variable. It still shows the old key and token values.

Is this an expected behaviour or a bug? Is there a solution or workaround for this issue?

Upvotes: 1

Views: 51

Answers (2)

Avraham Shalev
Avraham Shalev

Reputation: 110

This is not a bug but expected behaviour.

The api key in "MQTT settings" is used by the workbench to create and register virtual devices in the IoT-Platform service that is bound to the application.

The application will always take the credentials of the bound IoT-Platform service from VCAP_SERVICES.

Upvotes: 1

ValerieLampkin
ValerieLampkin

Reputation: 2626

Per this other stack overflow question, that tutorial is being updated.

IoT-Workbench now uses new improved code generation scheme for node.js. The document should be updated in the next few days for reflect the changes.

I will ask Avraham if he has any further update.

Upvotes: 1

Related Questions