Closed dsimog01 closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!
This issue or pull request has been automatically been closed due to inactivity.
When someone installs a new version of a package in which they have included
EXTRA_OPTS
, if this new version comes with any of the flags defined inEXTRA_OPTS
there is a duplication that causes the package to stop working.This is the solution we have thought of in the package side (for each package that includes
EXTRA_OPTS
):The docker-compose must include these envs: 1.1.
FLAGS
=> Will include the default flags for that package 1.2.EXTRA_OPTS
=> Will be empty by default and edited by the user if desired in the package config sectionThe command execution format in the
entrypoint.sh
will be the following:./command check_extra_opts(FLAGS, EXTRA_OPTS)
The package will include the file
check_extra_opts.sh
that needs to be copied to the image in build time and it wll be called as defined above in theentrypoint.sh
This
check_extra_opts.sh
file will return a "space separated" string removing the flags presents both inEXTRA_OPTS
andFLAGS
fromFLAGS
, giving priority to those introduced by the user (EXTRA_OPTS
)