Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More clear definition of APPDATA_PREFIX override value #2130

Open
kshychko opened this issue Feb 7, 2024 · 0 comments
Open

More clear definition of APPDATA_PREFIX override value #2130

kshychko opened this issue Feb 7, 2024 · 0 comments
Assignees

Comments

@kshychko
Copy link
Contributor

kshychko commented Feb 7, 2024

Expected Behaviour

Sometimes solution requires for deployment units to share the same APPDATA_PREFIX. In this case we can override it using DefaultFilePrefix setting

Current Behaviour

In order to do that DefaultFilePrefix settings needs to be defined in the component settings.json file.
But this file is also used to define a component settings for the purpose of setting env variables.

Possible Solution

We need to think of more clear way to define and use this settings as Hamlet engine feature and don't mix it with a component environment configuration.

Context

APPDATA_PREFIX was changed, when DefaultFilePrefix was removed from settings.json file and added to a deployment profile as a setting. It was ignored due to this change, which let to the problems for application to retrieve the existing files from S3 because of the incorrect prefix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants