Setting of environment variables

[Klaas-]

Hi,
please document how to set environment variables during the update run, the most prominent example of a package that needs env vars set in our environment is microsofts own odbc rpms:
ACCEPT_EULA=Y is needed in the environment variables for an update to succeed.

Old update management also loads /etc/environment but that does not seem to be documented anywhere.

Greetings
Klaas

[kjohn-msft]

Hi Klaas,

Thanks for the feedback on this.

We do not currently plan to set variables like ACCEPT_EULA on our own because the EULA is a legal agreement between the end customer and the package author.

For any generic set of environment variables to set, customers are encouraged to set them on Azure VMs using mechanisms like Run command:
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/run-command

For specific ones like ACCEPT_EULA, we will review that as a product request in our backlog, and get back to you.

Thanks,
Koshy

[Klaas-]

if there is no way to set environment variables you can not update Microsoft packages like msodbcsql17 with update management (https://packages.microsoft.com/rhel/8/prod/msodbcsql17-17.9.1.1-1.x86_64.rpm). That is also why update management v1 sets ACCEPT_EULA=Y inside it's runbook. I would much prefer a generic way via configfile or something similar :)

[shaneholder]

This seems to have been addressed with #215 but I am not finding any documentation on how to use the functionality. I see a reference to documentation on how to use it.

[shaneholder]

Based on the code it seems that a JSON file needs to exist
/var/lib/azure/linuxpatchextension/patch.eula.settings with contents of:

{
            "AcceptEULAForAllPatches": "True",
            "AcceptedBy": "TestSetup",
            "LastModified": "2023-08-29"
}

It would be great if someone on the team could confirm and document this.