`UBUNTU_STORE_AUTH_DATA_FILENAME` should be passed from Snapcraft to SnapD during build

[Jordan Garcia]

Couldn’t access a snap while building another snap with Snapcraft 7. After a while, the UBUNTU_STORE_AUTH_DATA_FILENAME parameter that was needed during the build process was discovered and worked afterwards.

Therefore, we should include UBUNTU_STORE_AUTH_DATA_FILENAME during the build process for SnapD if present.

[Callahan Kovacs (mr-cal)]

Hey Jordan,

A few questions:

How was this built - with LXD, Multipass, destructive-mode, or remote-build?

> Couldn’t access a snap while building another snap

What do you mean by "access"? Was it already installed? Was it a stage-snap or build-snap or manually installed?

> After a while, the UBUNTU_STORE_AUTH_DATA_FILENAME parameter that was needed during the build process was discovered and worked afterwards.

What was done for it to make it work?

[Jordan Garcia (jordanmg13)]

Hey Callahan! Thanks for the quick response!
This issue was reported by a customer in a (now old) case, and as such I'll answer with the best of my ability from the answers they gave us.

> How was this built - with LXD, Multipass, destructive-mode, or remote-build?

LXD and destructive mode was used.

> What do you mean by "access"? Was it already installed? Was it a stage-snap or build-snap or manually installed?

It seems like they couldn't download the snap from their store. The problem was using a relative path for the credentials file. They fixed it by using an absolute path instead.

> What was done for it to make it work?

They had to pass the same Snapcraft credentials file to SnapD with a parameter called UBUNTU_STORE_AUTH_DATA_FILENAME. They also used an absolute path to their credentials file instead.