About teracloud

According to your first link, it should be possible to manage the snap application's data via the web interface by writing the data to the $SNAP_COMMON/solutions folder. We tried to update our snapcraft.yaml file with the suggested solution, but we can't get it to work. What are we missing? Is there some kind of special requirement to get this active-solution plug working? Please keep in mind that this is a work in progress, but there is out current snapcraft.yaml file: name: teracloud # you probably want to 'snapcraft register <name>' base: core20 # the base snap is the execution environment for this snap version: '1.0' # just for humans, typically '1.2+git' or '1.3.2' summary: ControlMachines Logic # 79 char long summary description: ControlMachinesLogic grade: stable # must be 'stable' to release into candidate/stable channels confinement: strict # use 'strict' once you have the right plugs and slots type: app plugs: active-solution: interface: personal-files write: - $HOME/.config/foo passthrough: hooks: install: environment: CONFIG_NAME: Config.xml CONFIG_PACKED: ${SNAP}/bin/${CONFIG_NAME} #config location in the package (source) CONFIG_PATH: ${SNAP_USER_DATA}/${CONFIG_NAME} #config destination parts: src: plugin: dump source: ./src #dump files to root of the snap apps: copyconfig: command: bin/conf_upd.sh daemon: oneshot restart-condition: never # configtest: # command: bin/script.sh $CONFIG_PATH # daemon: oneshot # restart-condition: never # environment: # CONFIG_NAME: Config.xml # CONFIG_PACKED: ${SNAP}/bin/${CONFIG_NAME} #config location in the package (source) # CONFIG_PATH: ${SNAP_USER_COMMON}/${CONFIG_NAME} #config destination GenAddrCacheEMA: command: bin/ControlMachinesLogic $CACHE_NAME daemon: oneshot plugs: - mount-observe - network - network-status - network-bind - active-solution: interface: content content: solutions target: $SNAP_COMMON/solutions restart-condition: never environment: DOTNET_SYSTEM_GLOBALIZATION_INVARIANT: 'true' CACHE_NAME: -GenMonitorAddrCache:EMA -Environment:Bosch viewconfig: command: bin/printconfig.sh daemon: oneshot restart-condition: never app: command: bin/ControlMachinesLogic $RUNTIME daemon: simple plugs: - mount-observe - network - network-status - network-bind - active-solution: interface: content content: solutions target: $SNAP_COMMON/solutions restart-condition: on-failure passthrough: restart-delay: 10s environment: DOTNET_SYSTEM_GLOBALIZATION_INVARIANT: 'true' RUNTIME: -Logic:EMA -Environment:Bosch # SNAP_USER_COMMON unversioned user specific storage # SNAP_USER_DATA versioned user specific storage # SNAP_DATA/SNAP_COMMON system-wide data storage to share between snaps We are running snapcraft via github. When we do, we get the following error: Starting Snapcraft 7.1.3 Logging execution to '/home/user/.cache/snapcraft/log/snapcraft-20220906-145237.288545.log' Issues while validating snapcraft.yaml: The 'apps/GenAddrCacheEMA/plugs[4]' property does not match the required schema: OrderedDict([('active-solution', OrderedDict([('interface', 'content'), ('content', 'solutions'), ('target', '$SNAP_COMMON/solutions')]))]) is not of type 'string'  What could be the problem? ... View more

Lots of interesting information to look at. Thank you for the information! ... View more