- 最新
- 最多得票
- 最多評論
Hi again TSpark,
I'd suggest that you create a component to hold the device-unique configurations you need. Let's call it simply "Config". You will create a deployment for each device that needs its own values and you will deploy only "Config". In the deployment, you will merge in the device-specific values.
Components in the group deployment which need device-specific information can use our GetConfiguration API in order to read the configuration. If you do not want to use IPC, then the configuration can also be interpolated into the component's lifecycle such as {Config:configuration:/configPath}
, where "Config" is your config component name.
As another simple option if the configuration is going to be static, then of course you could simply have a file on the device that contains whatever unique information it needs.
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
Awesome, thanks for all the answers ! It is really helping our migration
Having a config component and reverencing its config in another component seems to work nicely. Is it possible to use that variable to get a different artifact ? I would like to have an artifact similar to "URI": "S3://bucket/{com.comp.test:configuration:/script_name}". Alternatively, I would be okay to get the whole folder or all files in the S3 folder, but that also does not seem to work
No, you cannot use variables for artifacts. The artifacts must be known at the time that the component version is created. That being said, your component could just use the S3 API or AWS CLI to download whatever you want from S3.