Disable Archival feature in development docker

[feedmeapples]

What changed?
development-*.yaml docker configs now set archival feature to "disabled" by default.
Added development_archival.yaml that has archival "enabled"

Why?
File based implementation of archival feature may not be the best to be enabled by default as it can bloat up the storage.

How did you test it?

• Built a new docker image
  docker build -t temporalio/server:test .
• Span it up using docker-compose up
• tctl namespace desribe
  

Potential risks
No risks

[samarabbas]

You want to also update config_template.yaml used by docker builds:
https://github.com/temporalio/temporal/blob/master/docker/config_template.yaml

[markmark206]

just curious – were you able to start temporal server using this config file? if not, i wonder if it is worth it to postpone adding development_archival.yaml until we release tested/supported archival feature and have a chance to really test this. (not a blocker for this merge, of course, just thinking out loud).

[feedmeapples]

@markmark206 this configuration is the same as the previous development.yaml which had archival enabled and that we've been running. Should we do a separate testing of it?

[markmark206]

we talked about testing all config files at some point, but until then, just running ./temporal-server -e development_archival start would be enough. (since this is a copy paste of another file, it's likely it just works, and it's not breaking any workflows, so i think this is also fine as is.)

[feedmeapples]

tested and i can see the default archival state set to Enabled if started using development_archival config

Registering new namespace (tctl --namespace n1 namespace register) results in this state of archival:

[samarabbas]

Can you file a separate issue to make this docker parameter which users can control?

[feedmeapples]

Created a ticket #623 Add control of archival feature initial state through docker-compose parameter.

Does this mean that the variable will override the archival state set in defaultNamespace of temporal config?