applicationConfigVariables in balena.yml not working correctly?

shawaj · December 23, 2022, 4:49am

When I try to apply the application config variable from a balena.yml using the deploy with balena method, the value RESIN_HOST_CONFIG_disable_splash: 1 fails to populate correctly. The other config variables seem to populate just fine.

See screenshot here:

You can see the repo here:

And the balena.yml is here:

github.com

NebraLtd/helium-rak/blob/master/balena.yml

name: nebra-helium-rak
type: sw.application
description: >-
  Manage your RAK v1.5, v2 or MNTD Helium Miner remotely using Nebra and balenaCloud.
post-provisioning: >-
  ## Usage instructions
  
  
  Once your device joins the fleet you'll need to allow some time for it to download the application and start forwarding packets to the Helium Network.
  
  
  For detailed instructions on how to use Nebra Helium RAK check out [our GitHub repo](https://github.com/NebraLtd/helium-rak).
  
  
  For support you can [open an issue](https://github.com/NebraLtd/helium-rak/issues) on the repo or reach out to us via one of the methods listed [on our support page](https://helium.nebra.com).
assets:
  repository:
    type: blob.asset
    data:
      url: "https://github.com/NebraLtd/helium-rak"

This file has been truncated. show original

Is this a known issue?

alanb128 · December 27, 2022, 4:50am

Hello @shawaj this does not seem to be a known issue. I was also able to reproduce it. I’ll ask internally and if necessary we’ll open an issue and keep this thread updated.

shawaj · December 27, 2022, 5:39pm

Thanks @alanb128 much appreciated

myarmolinsky · December 27, 2022, 7:03pm

Hello, this sounds like it may actually be an internally known issue (I would share the github issue but unfortunately it is in a private repository). Could you please check if putting the value that fails to populate correctly in quotes fixes the problem?

myarmolinsky · December 27, 2022, 7:11pm

Ah actually you mentioned you were deploying with balena, implying you do not have edit access to the balena.yml for testing with DWB, right? In that case I would raise an issue in the respective repository to inform the maintainer to check out this issue, and inform them that we have an internal issue with a suggested workaround of putting the “bad” value in quotes. If you do create the issue, please link it here for visibility for anyone coming here with the same issue to be able to keep an eye on it.

shawaj · December 27, 2022, 8:16pm

@myarmolinsky - actually it is our repo, so I do have access.

I did try putting it in quotes before and it made no difference. I just tried it again and it made no difference.

However, trying on an incognito browser window a few minutes later, it did work. However, I can’t seem to reproduce this.

Does the deploy with balena button use some kind of server-side caching of the balena.yml file in a repo or something? Is there any way we can force-clear that cache?

shawaj · December 28, 2022, 11:42am

@myarmolinsky just FYI I’ve managed to reproduce it working reliably with:

    - RESIN_HOST_CONFIG_disable_splash: "1"

There definitely seems to be some caching of the balena.yml so changes aren’t pulled through immediately but it does not seem to work correctly.