You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a manifest which includes fixtures which are configurable via values.yaml.
Additional Information
Use {{ toYaml .Values.geonodeFixtures | nindent 2 }} to include the fixtures.
Not sure about auto loading the fixtures via python manage.py loaddata <yourfixturehere>. For now this would have be done manually. What is your opinion on this @mwallschlaeger ?
The text was updated successfully, but these errors were encountered:
I'm open to this idea. Using the current deployment will run into problems when using not vanilla geonode implementations. so make the helm chart aware of things like fixtures and so on is a plus. As geonode4.2 also targets a new init process for their django geonode container, this helm chart is open to initialize the deployment also apart from tasks.py.
But for now i think defining fixtures inside the values.yaml could add a function call inside of tasks.py.
Task Description
It would be nice to have a manifest which includes fixtures which are configurable via
values.yaml
.Additional Information
{{ toYaml .Values.geonodeFixtures | nindent 2 }}
to include the fixtures.Not sure about auto loading the fixtures via
python manage.py loaddata <yourfixturehere>
. For now this would have be done manually. What is your opinion on this @mwallschlaeger ?The text was updated successfully, but these errors were encountered: