Currently we thought to sign the host as part of vdsStatic fields. It will allow to recognize the host as managed by foreman and gather more information about its configuration status
(In reply to Yaniv Bronhaim from comment #0) > Currently we thought to sign the host as part of vdsStatic fields. It will > allow to recognize the host as managed by foreman and gather more > information about its configuration status I'd suggest to add the host_provider_id field to vdsStatic in order to accomplish that.
This looks like a code change and it seems there is nothing to be tested here. If you think otherwise, please provide steps to reproduce.
testcase: Go to engine, add host by external provider. check the provider id in db (select * from providers) and check that the value correlates to the value in vds_static::host_provider_id (select host_provider_id from vds_static;) except that, check that host which added regularly gets none in its host_provider_id column.
host_provider_id is empty in vds_static: select vds_name,host_provider_id from vds_static ; vds_name | host_provider_id ----------+------------------ host1 | (1 row)