Hello Satyam Chauhan,
you have created a custom Azure IoT Edge module but you do not want it to configure using C2D twin messages.
Normally, if you want to manipulate an Azure IoT Edge module when it starts, you use Module twin desired properties. These are originally coming from the IoT Hub but the Edge Hub can hand them out also for offline scenarios.
An alternative is using environment variables as seen in the generic configuration of docker containers. Using these environment variables is also supported in the Deployment manifest for each module.
As seen in this C# example, modules can access these variables as regular environment variables:
var variables = Environment.GetEnvironmentVariables();
Console.WriteLine($"Found {variables.Count} Environment variables:");
foreach (DictionaryEntry variable in variables)
{
Console.WriteLine($"Environment variable '{variable.Key}': '{variable.Value}'");
}
Remember, if you use this and you want to change a variable, you need to deploy a new version of the Deployment manifest.
Potentially, this can have an impact on all other modules running on the same edge (eg. getting a new set of the same twins). Please double-check this potential behavior.