NETConfig

The netconfig AS A DATABASE. One NETSetupConfig = one V5 data store, served through the very same IVirtualizationUnitOfWork a Hyper-V scope and a Proxmox node are served through.

Note

The chain is: company → translator → NETSetupConfig → THIS store. What used to be "the precalculated target environment" is now simply the SOURCE data store, and installing a customer is a synchronisation between two stores of the same shape:

netconfig (source)  --read-->  records  --insert/update-->  Hyper-V / Proxmox (target)  --commit-->

Sqlite would be the usual backing store of a source database; here the backing store is the customer JSON, which is what the translator produced.

var provider = new DataStoreReferenceProvider3.Builder()
    .AddReference3<NETConfig.DBBuilder>(b => b.WithConfig(config))
    .Build();

public sealed class NETConfig : VmDataStoreReferenceBase<NETConfig>

1. Constructors

1.1. NETConfig(VmConnectionStringBuilder, IKeyedServiceProvider, NETSetupConfig)

Initialises a new instance of the NETConfig class.

public NETConfig(VmConnectionStringBuilder connectionStringBuilder, IKeyedServiceProvider keyedServiceProvider, NETSetupConfig config)

Table 1. Parameters
Name	Type	Description
connectionStringBuilder	VmConnectionStringBuilder	Connection string carrying the store key.
keyedServiceProvider	IKeyedServiceProvider	Service provider.
config	NETSetupConfig	The config that IS the data store.

2. Fields

2.1. ProviderName

Data store provider name of a netconfig-backed store.

public const string ProviderName

3. Properties

3.1. Config

Gets the config this store serve.

public NETSetupConfig Config { get; }

3.2. Operations

Gets the environment operations seam of this reference.

protected override IVirtualMachineOperations Operations { get; }