Page MenuHomePhabricator

[services] Dev Mode - Apply local cloud to the Backup service
AbandonedPublic

Authored by karol on Mar 23 2022, 7:58 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 13, 12:43 PM
Unknown Object (File)
Tue, Nov 5, 4:32 PM
Unknown Object (File)
Oct 13 2024, 12:28 PM
Unknown Object (File)
Oct 13 2024, 12:28 PM
Unknown Object (File)
Oct 13 2024, 12:14 PM
Unknown Object (File)
Oct 10 2024, 6:06 PM
Unknown Object (File)
Oct 2 2024, 11:11 PM
Unknown Object (File)
Sep 8 2024, 5:28 AM

Details

Summary

Depends on D3497

This replaces the old approach to the dev mode in the backup service with the local cloud.

Test Plan
cd services
yarn run-local-cloud
yarn setup-local-cloud
yarn run-backup-service-dev-mode

Diff Detail

Repository
rCOMM Comm
Branch
localstack
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Putting @jimpo as blocking to make sure we're thinking about Docker / Docker Compose correctly

jim requested changes to this revision.Apr 4 2022, 1:33 PM
jim added inline comments.
services/backup/docker-server/contents/server/src/AwsTools.cpp
10

I don't like that this is a compile-time flag. This is runtime configuration. It'd be better to load this from an actual AWS config file or other type of config file, or at the very least command line options or environment variable.

This revision now requires changes to proceed.Apr 4 2022, 1:33 PM
services/backup/docker-server/contents/server/src/AwsTools.cpp
10

We have to read this from the command line. It cannot be read from any config file. The parameters in config files are constant. And having the same files' state we want to be able to run both normal mode and dev mode.
If we want to avoid compiler flags, I think we need to read the environment variables in the c++ code in the runtime.
Reading it from the command line arguments doesn't seem like a good idea - this will not scale well. If the number of such parameters grows, the code's going to get quite messy.

I changed my approach, now I used terraform for this. I'm abandoning this one. I decided that it will be faster to set up a new stack as I reordered the diffs and a lot of the differed from the ones from this stack. Let's follow up in the stack beginning at D3695.