services/horizon/docker/ledgerexporter: deploy ledgerexporter image as service #4490
Conversation
…exporter_as_service
| @@ -91,7 +93,7 @@ func main() { | |||
| err = core.PrepareRange(context.Background(), ledgerRange) | |||
| logFatalIf(err, "could not prepare range") | |||
|
|
|||
| for nextLedger := startLedger; nextLedger <= endLedger; { | |||
| for nextLedger := startLedger; endLedger < 1 || nextLedger <= endLedger; { | |||
There was a problem hiding this comment.
during testing with END=0, ran into this as it was stopping before generation anything
historyarchive/s3_archive.go
Outdated
| @@ -121,7 +121,6 @@ func (b *S3ArchiveBackend) PutFile(pth string, in io.ReadCloser) error { | |||
| params := &s3.PutObjectInput{ | |||
| Bucket: aws.String(b.bucket), | |||
| Key: aws.String(key), | |||
| ACL: aws.String(s3.ObjectCannedACLPublicRead), | |||
There was a problem hiding this comment.
Current txmeta bucket uses policy for auth, which requires credentials(access key/id) from an IAM principal(I initially used a user in the AWS account, need to create a non-user service account) but when using policy on s3 bucket, it can trigger auth error if explicit ACLs are set by client when updating the bucket, and this ACL was causing AccessControlListNotSupported
I can either change the new txmeta bucket to be ACL based and revert this, or we go with the AWS recommendation on s3 bucket policy and migrate existing buckets by adding a policy to them which has Allow statement Public Read. Noticed only 3 buckets on S3 at present and this was the only sdk usage of s3 ACLs, I see other s3 usages that don't send the ACL.
There was a problem hiding this comment.
I went with alternative approach and added ACL config option - 452b20c, this way client can work with buckets in either permissions config.
| volumes: | ||
| - name: tempfs-volume | ||
| emptyDir: | ||
| medium: Memory |
There was a problem hiding this comment.
captive core's on-disk db(stellar.db) will be on this tempfs RAM drive
There was a problem hiding this comment.
scratch that, after further testing on cluster, found the tempfs ram was not suitable/stable for captive core on-disk db usage, the size of this volume is derived from the underlying host k8s node RAM, and is limited by default to half, so, it's variable, anytime the pod restarts it could end up running on a diff node with different RAM and I saw a few OOMKilled due to this, switched volume to use a PV/PVC.
| name: ledgerexporter-pubnet-secret | ||
| type: Opaque | ||
| data: | ||
| AWS_REGION: <base64 encoded value here> |
There was a problem hiding this comment.
AWS credentials get loaded into the cluster as secrets, which deployment pulls into ledgerexporter container as env variables.
| CAPTIVE_CORE_USE_DB: "true" | ||
| HISTORY_ARCHIVE_URLS: "https://history.stellar.org/prd/core-live/core_live_001,https://history.stellar.org/prd/core-live/core_live_002,https://history.stellar.org/prd/core-live/core_live_003" | ||
| NETWORK_PASSPHRASE: "Public Global Stellar Network ; September 2015" | ||
| ARCHIVE_TARGET: "s3:https://horizon-ledgermeta-pubnet" |
There was a problem hiding this comment.
i've config'd the horizon-ledgermeta-pubnet bucket in same AWS account as Batch, with bucket owner enforced with ACLs disabled and a inline policy that defines allowed/disallowed statements, following aws recommendations .
There was a problem hiding this comment.
You mean you changed the existing bucket settings?
Unfortunately the S3-writing code (HistoryArchive) code assumes ACLs are enabled (because it writes them). That's why they where enabled.
I am not against the change but then we should also change the writing code.
There was a problem hiding this comment.
I haven't changed any existing bucket permissions, but this looks fairly constrained on ACL usage though, only one place in s3 writing code sets the object ACL to include public read during put which I removed and left a comment on one potential to migrate off that.. There are several other places where s3 object writing(puts) are done with s3uploadmanager and those don't specify ACLs.
So, the net seems to be in identifying how many existing buckets which could have been written to by this routine in historyarchive/s3_archive.go. With just removal of ACL here, the net effect is that put still works to the existing buckets but the objects won't have public read until the bucket permissions are updated to have ACL's disabled and a policy added with statement for Allow Everyone/Public Read.
There was a problem hiding this comment.
I updated approach and added ACL config option on s3 - 452b20c, this way client can work with buckets in either permissions config.
There was a problem hiding this comment.
@2opremio , I added more to permissions on horizon-ledgermeta-prodnet-test and horizon-index, added policy to grant write to ec2(Batch access) and an IAM user(k8s access) and a PublicRead rule.
I noticed slight diff on their main config, horizon-ledgermeta-prodnet-test had ACLs enabled/bucket owner preferred, and horizon-index had ACLs disabled/bucket owner enforced. The policy applies on top of either.
…pod resource limits
…exporter_as_service
|
The deployment is active on the dev k8s cluster, logs here |
| @@ -150,7 +150,6 @@ func (b *S3Storage) PutFile(pth string, in io.ReadCloser) error { | |||
| params := &s3.PutObjectInput{ | |||
| Bucket: aws.String(b.bucket), | |||
| Key: aws.String(key), | |||
| ACL: aws.String(s3.ObjectCannedACLPublicRead), | |||
There was a problem hiding this comment.
Ahhh, I see you changed it here. Is this horizon-light-only code? Otherwise we would need to check whether it breaks something.
There was a problem hiding this comment.
yes, I was wondering the same on usage, it seems like it may be contained to just the AWS Batch account S3 for horizon light ledgerexport?
There was a problem hiding this comment.
Does the git blame on this line have any meaningful history behind it? I'm pretty sure this storage backend is used by Horizon (though maybe not by SDF's deployments), but I'm not sure.
There was a problem hiding this comment.
Yeah, that ACL has been there since 2017, so, could be used in various ways, @bartekn , do you have insight on types of usages of S3Storage.PutFile, like which SDF S3 buckets has it been used or is it used by customers for their own S3 stuff?
I think I'm going to revert this line, leave that ACL in to avoid unraveling, and instead add ConnectOptions.DisableS3ACL and S3Storage.disableS3ACL , ledgerexporter can then set that to true when invoking ConnectBackend, lmk if any thoughts either way, thx!
There was a problem hiding this comment.
ok, I went with that change and added config option to override the S3 File ACL rule applied - 452b20c
bucket owner policy works with ObjectCannedACLBucketOwnerFullControl
There was a problem hiding this comment.
Good! Will the code still work if we remove ACL support from the bucket? (which is what AWS recommends)
There was a problem hiding this comment.
It will if client is the bucket owner, and for any other prinicipals that should have access, adding an inline policy on the bucket with allow statements should provide write and read rules, I added such a policy doc to horizon-ledgermeta-prodnet-test, I noticed horizon-index-prodnet-test had ACLs disabled with owner enforced already, but it doesn't have policy set yet, we can update that for Public(read) and other principals like k8s, which would need read for web and write for single indexer(watching for latest).
…ardcoded assumption
…exporter_as_service
…eta bucket and run in append/continue mode
👍
* exp/lighthorizon: Add initial support for XDR serialization (#4369) * exp/lighthorizon: Improve trie tests to avoid raw comparisons/outputs. (#4373) * exp/lighthorizon: Add XDR marshalling for the `TrieNode` structure. (#4375) * Add encoding stdlib interfaces * lighthorizon: Sync with upstream master branch (#4404) * services/ticker: ingest assets optimizations (#4218) * Add CHANGELOG entry for Horizon 2.14.0 release (#4208) (#4220) * Make sure we test reingestion for all possible operations (#4231) * services/horizon: Allow captive core to run with sqlite database (#4092) * services/horizon: Release DB connection in /paths when no longer needed (#4228) * services/horizon: Exclude trades with >10% rounding slippage from trade aggregations (#4178) * all: staticcheck fixes (#4239) * Migrate Horizon integration tests to GitHub Actions (#4242) * Fix StreamAllLiquidityPools and StreamAllOffers (#4236) * all: run builds and tests with go1.18rc1 (#4143) * all: cache go module downloads and other build and test artifacts (#3727) * services/horizon: Add LedgerHashStore to Captive-Core config (#4251) * all: migrate the rest of the CircleCI jobs to GitHub Actions (#4250) * horizon: Fix GitHub action problem with verify-range push in master (#4253) * all: fix ci ref_protected check for caching (#4254) * Switch over from CircleCI to GitHub A tions (#4256) * all: [GitHub actions] Reset the module and build cache in master/protected (#4266) * Forgot to add sudo in #4266 (#4270) * all: More go-setup github action fixes (#4274) * xdr: add instructions for generating xdr (#4280) * services/ticker: cache tomls during scraping (#4286) * services/ticker: use log fields during asset ingestion (#4288) * services/ticker: reduce size of toml cache in memory (#4289) * historyarchive: add --skip-optional flag (#3906) * all: Add Protocol 19 XDR and update StrKey to support Signed Payloads (#4279) * Replace keybase with publicnode in the stellar core config (#4291) * Fix captive core tests to write to /tmp, instead of polluting the repo (#4296) * all: remove go1.16 add go1.18 (#4284) * Rename methods and functions in submission system (#4298) * PR feedback (#4300) * Support new account fields for protocol-19. (#4294) * xdr, keypair: Add helpers to create CAP-40 decorated signatures (#4302) * services/horizon: Update txsub queue to account for new CAP-21 preconditions (#4301) * Uncomment StateVerifier test that generates account v3 extensions now that they are implemented. (#4304) * txnbuild: Add support for new CAP-21 preconditions. (#4303) * services/horizon: Support new CAP-21 transaction conditions (#4297) * txnbuild: Complete rename, avoid using XDR types in `TransactionParams`. (#4307) * all: Update Protocol 19 XDR to the latest (#4308) * services/horizon: Add a rate limit for path finding requests. (#4310) * clients/horizonclient: fix multi-parameter url for claimable balance query (#4248) * all: Fix Horizon integration tests (#4292) * horizon: Fix integration tests (#4314) * horizon: Set up protocol 19 integration tests infrastructure (#4312) * all: Change outdated CircleCI build badge (#4324) * horizon: Test new protocol 19 account fields (#4322) * all: update staticcheck to 2022.1 (#4326) * all: remove go.list and related docs (#4328) * horizon: Add transaction submission test for Protocol 19 (#4327) * Horizon v2.16.1 CHANGELOG (#4333) * Revert "Pin go versions temporarily" (#4338) * services/horizon: Use `bigint` over `timestamp` to accommodate large years (#4337) * xdr: Update xdrgen (#4341) * services/horizon: Change `min_account_sequence_age` column from `bigint` to string (#4339) * services/horizon: Bump stellar-core to v19.0.0rc1 for Horizon tests (#4345) * services/horizon: expose supported protocol version on root endpoint (#4347) * horizon: Small transaction submission refactoring (#4344) * services/horizon: Pass through nil ExtraSigners to avoid nil pointer deref (#4349) * doc: rename license file (#4350) * all: upgrade dep github.com/valyala/fasthttp (#4351) * services/horizon: Promote Stellar Core to v19.0.0 stable. (#4353) * services/horizon/integration: Precondition edge cases and V18->19 upgrade boundary. (#4354) * xdr: Synchronizes monorepo XDR with Stellar Core (#4355) * services/horizon: Properly allow nullable Protocol 19 account fields (#4357) * services/friendbot: include txhash in logs (#4359) * services/horizon: Improve transaction precondition `omitempty` behavior (#4360) * tools/horizon-cmp: Improve panic error message (#4365) * services/horizon: Merge stable v2.17.0 back into master: (#4363) * Use UNIX timestamps instead of RFC3339 strings for timebounds. (#4361) * xdrgen: remove gemfile and rakefile to just use docker for the xdrgen (#4366) * Conservatively limit the number of DB connections of integration tests (#4368) * internal/integrations: db_test should drop test db instances when finished (#4185) * GHA: Bump Core version to v19.0.1 in Horizon workflows. (#4378) * services/horizon, clients/horizonclient: Allow filtering ingested transactions by account or asset. (#4277) * Push stellar/ledger-state-diff images from Github actions (#4380) * services/horizon: Fixes copy-paste typo in `--help` text (#4383) * tools/alb-replay: Add new features to alb-replay (#4384) * services/horizon: Optimize claimable balances query to limit records earlier (#4385) * support/db, services/horizon/internal: Configure postgres client connection timeouts for read only db (#4390) * Refactor trade aggregation query. (#4389) * services/horizon/internal/db2/history: Implement StreamAllOffers using batches (#4397) * Add flag to disable path finding endpoints (#4399) Co-authored-by: stfung77 <[email protected]> Co-authored-by: Leigh McCulloch <[email protected]> Co-authored-by: Alfonso Acosta <[email protected]> Co-authored-by: Paul Bellamy <[email protected]> Co-authored-by: Bartek Nowotarski <[email protected]> Co-authored-by: tamirms <[email protected]> Co-authored-by: Alfonso Acosta <[email protected]> Co-authored-by: Graydon Hoare <[email protected]> Co-authored-by: Satyam Zode <[email protected]> Co-authored-by: Satyam Zode <[email protected]> Co-authored-by: erika-sdf <[email protected]> Co-authored-by: iateadonut <[email protected]> Co-authored-by: Shawn Reuland <[email protected]> Co-authored-by: shawn <[email protected]> Co-authored-by: Shivendra Mishra <[email protected]> Co-authored-by: Jacek Nykis <[email protected]> Co-authored-by: jacekn <[email protected]> * Explain map and reduce commands * exp/lighthorizon: Refactor single-process index builder. (#4410) * Refactor index builder: - allow worker count to be a command line parameter - split work by checkpoints rather than ledgers - move actual index insertion work to helpers - move progress bar into helpers - simplify participants code, payments vs. all * Properly work on a checkpoint range at a time: - previously, it was just arbitrary 64-ledger chunks which is not as helpful * Define a generic module processing function * Move index building into a separate object * Fix off-by-one error in checkpoint index builder: - Keeping this as-is would mean that the first chunk of ledgers will be "Checkpoint 0" which doesn't make sense in the bitmap - Calling index.setActive(0) is essentially a no-op, because no bit will ever be set. - In the case of an empty index in which the only active account checkpoint is the first one, this is indistinguishable from an index with no activity. * exp/services/ledgerexporter: Extend tool to support lower ledger bound. (#4405) * exp/lighthorizon: Refactor and repair the reduce job (#4424) * Use envvars for every configurable thing, incl. index sources and final merged index target: This removes any hard dependency on S3 and lets you use any supported backend for the map-reduce operation. It was done specifically with local filesystem-based testing in mind, but naturally opens up other backends as well. * Add lots of helper functions: Specifically, helpers now exist for both merging two sets of named indices together and partitioning work based on the account/transaction hashes into separate jobs/routines. * Lots more logging! For progress tracking, debugging, etc. * Create a thread-safe string set abstraction for tracking completed work. * Better error handling: `os.IsNotExist(err)` is much more reliable over a direct equality check to `ErrNotExist`. This also ties in to backend-independence. We can also log and return an error rather than immediately panicking on its occurrence. * Transaction flushes need to be thread-safe if they're going to be done from different goroutines during reduction. Otherwise, you get panics from concurrent writes to its maps. * The "account list" (aka the file containing a list of all accounts in the partitioned index) needs to be flushed at the same time as the index itself: If this isn't done, then `FlushAccounts()` will do absolutely nothing after a `Flush()`, because the previous `Flush()` will clear the map of indices out of memory. Since the account list comes from memory, it becomes a no-op. * Split work across multiple channels rather than just one If the work comes from a single channel, accounts can get skipped overall because they aren't put back on the queue if they're skipped by a single worker. It makes more sense to make each worker have its own channel, partitioning the work *before* it gets to the worker rather than after. * exp/lighthorizon: Unify map-reduce and single-process index builders (#4423) * Main thing: `./index/cmd/single` and `./index/cmd/batch/map` now leverage the same index building code (i.e. `BuildIndices`) * This also extends the map-reduce builder to take the txmeta source / index destination URLs from envvars rather: This eliminates a hard dependency on S3, and it's done here because splitting that out from the giga-PR was difficult. * We can infer checkpoints from `ledger.LedgerSequence()` rather than passing them in as a parameter, which cleans up modules. * This finally adds a new `ProcessAccountsWithoutBackend` module for the Map job * exp/lighthorizon: Thread-safe support for reading account list via FileBackend (#4422) Three key changes: - actually read the account list when using a filesystem backend - using `O_APPEND` on the file to support concurrent writes - ensure that the read list is a unique set of accounts * exp/lighthorizon: Restructure index package into sensible sub-packages (#4427) * exp/lighthorizon: Merge on-disk index with in-memory one on load. (#4435) * Add test for single-process index builder * Merge in-memory index with on-disk one when loading * Add fixture of unpacked ledgers for fast local testing * Isolate the index we need to merge * Use a ByteReader so that multiple indices in one file work 🤦 * Add to/from XDR support to bitmap index * Fix and extend gzip tests to handle the bytereader bug * Simplify participant processing code * exp/lighthorizon: Allow indexer to continually update as new txmeta appears (#4432) * exp/lighthorizon: enforce the limit from request on the response size (#4431) * Dockerize ledgerexport to run in AWS Batch This Change: 1. Creates docker image (stellar/horizon-ledgerexporter) which works in a similar fashion to stellar/horizon-verify-rage and is tested and pushed as part of the Horizon GitHub workflow. 2. Adds two more parameters to ledgerexporter * --end-ledger: which indicates at what ledger to stop the export * --write-latest-path: which indicates whether to udpate the /latest path of the target Latest path writing is disabled in the container by default in order to avoid race-conditions between parallel jobs * exp/lighthorizon: Add test for batch index building map job (#4440) * Modify single-process test to generalize to whatever fixture data exists This also adds a test to check that single-process works on a non-checkpoint starting point which is important. * Fix map program to properly build sub-paths depending on its job index Previously, this only happened for explicitly S3 backends. * Make map job default to using all CPUs * Stop clearing indices from memory if using unbacked module * Use historyarchive.CheckpointManager for all checkpoint math * Update lastBuiltLedger w/ safely concurrent writes * Refactor bound preparation and add --continue flag * Address review feedback and rework env variable names * Run gofmt -w (I don't know why those files were changed) * Add proper logging to indicate what range is being exported * Add clarification about end ledger * Fix boolean argument passing * Address review feedback * Address feedback * Use sqlite for captive core * exp/lighthorizon: Add basic scaffolding for metrics. (#4456) * Use correct network passphrase when populating transaction * Add scaffolding for Prom/log metrics and some example ones * Misc. clarifications and fixes to the index builder * lighthorizon: Prepend version to ledger files (#4450) * Prepend version to ledger files * Encode versioning in XDR * Regenerate fixtures * Fix ledger fixtures * Appease govet * Move all lighthorizon types to /xdr * exp/lighthorizon/index: More testing for batch indexing and off-by-one bugfix. (#4442) * Add reduce test to ensure combining map jobs works * Actually test that TOIDs are correct * Bugfix: Transaction prefix loop should be inclusive * Isolate loggers to individual processing "sections" * Minor ledgerexporter infrastructure improvements (#4461) * Push the stellar/horizon-ledgerexporter docker image when pushing to the lighthorizon branch * Fix the ledger exporter aws batch jobs when running on the first batch * Forgot to add login step to ledgerexporter workflow * exp/lighthorizon: Set a default number of workers. (#4465) * Default to the number of CPUs if worker count isn't specified * Set a timeout on the reduce job to avoid test suite hanging indefinitely * exp/lighthorizon: Fix the single-process index builder data race. (#4470) * Add synchronization for the work submission routine. Thank you @sreuland! Co-authored-by: shawn <[email protected]> * /exp/lighthorizon: new endpoints for tx and ops paged listing by account id (#4453) * exp/lighthorizon: Add an on-disk cache for frequently accessed ledgers. (#4457) * Replace custom LRU solution with an off-the-shelf data structure. * Add a filesystem cache in front of the ledger backend to lower latency * Add cache size parameter; only setup cache if not file:https:// * Extract S3 region from the archive URL if it's applicable. * exp/lighthorizon/index: Drop building indices for successful transactions. (#4482) * Add metrics middleware to collect request duration metrics (#4486) * exp/lighthorizon: Isolate cursor advancement code to its own interface (#4484) * Move cursor manipulation code to a separate interface * Small test refactor to improve readability and long-running lines * Combine tx and op tests into subtests * Fix how IndexStore is mocked out * exp/lighthorizon/index: Parse network passphrase from the env. (#4491) * Refactor access to meta archive (#4488) Refactor `historyarchive` and `ledgerbackend` to allow better access to the new meta archives: * Created `metaarchive` package that connects to the new meta archives (and allows accessing `xdr.SerializedLedgerCloseMeta`). * Extracted `ArchiveBackend` to the new `support/storage` package as it contains only storage related methods. New package is used in both `historyarchive` and `metaarchive`. * exp/lighthorizon: Add response age prometheus metrics (#4492) * exp/lighthorizon/index: Allow accounts to be indexed by ledger. (#4495) * Add builders to make account indices by ledger * Add `MODULE` parameter to map job in batch builder * Don't build transaction indices by default * services/horizon/docker/ledgerexporter: deploy ledgerexporter image as service (#4490) * Make indexing s3 bucket configurable (#4507) * exp/lighthorizon: Add duration metrics for on-the-fly ingestion elements. (#4476) Add basic aggregate metrics for request fulfillment: - how long did ledger downloads take, on average? - how long did ledger processing take, on average? - how long did index lookups take, on average? - how many ledgers were needed? - how long did the entire request take, in total? * exp/lighthorizon: Add JSON content type to responses. (#4509) * exp/lighthorizon: *Correctly* set `Content-Type`, plus JSONify errors (#4513) * exp/lighthorizon/services: Move service-specific stuff to its own file. (#4502) * exp/lighthorizon, xdr: Rename `CheckpointIndex` to better reflect its capabilty. (#4510) * Rename NextActive -> NextActiveBit to be descriptive * exp/lighthorizon: Add a suite of tools to manage the on-disk ledger cache. (#4522) * Run 'go mod tidy' after merge * exp/lighthorizon: add horizon web docker/k8s deployment (#4519) * It seems like the merge caused some deleted files to stay in: The commit b3407fd from PR #4418 deleted these files, so we just do the same. A quick manual inspection showed us that the deltas transferred over, just not the deletions, for some reason. Idk why these changes ended up in the code, kinda sus... More deleted files snuck in? * One more that didn't get removed 🤔 * all: Incorporate generics into Light Horizon code. (#4537) * bump go version to 18 on lighthorizon docker images, they need it now (#4541) * exp/lighthorizon/actions: use standard Problem model on API error responses (#4542) * exp/lighthorizon/build/index-batch: carry over map/reduce updates to latest docker layout on feature branch (#4543) * exp/lighthorizon: Properly transform transactions into JSON. (#4531) * exp/lighthorizon: Add a set of tools to aide in index inspection. (#4561) * exp/lighthorizon/cmd: index batch fix s3 sub paths in reduce (#4552) * exp/lighthorzon: Add a generic, thread-safe `SafeSet`. (#4572) * support/storage: Make the on-disk cache thread-safe. (#4575) * exp/lighthorizon: Incorporate tool subcommands into the webserver. (#4579) * exp/lighthorizon/index/cmd: Fix index single watch, slow down the retry on not-found ledgers (#4582) * exp/lighthorizon: Refactor archive interface and support parallel ledger downloads. (#4548) - Refactor and simplify Archive abstraction to incorporate MetaArchive - Actually add & use parallel downloads, preparing checkpoint chunks - Fix test structures and mocking - Fix cache to ignore on-disk if lockfile present * exp/lighthorizon: Minor error-handling and deployment improvements. (#4599) - actually set the PARALLEL_DOWNLOADS parameter to use #4468 - return a 404 rather than a 500 if a ledger is missing as its more descriptive - handle `count = 0` in average metric calculations * exp/lighthorizon/index: Add ability to disable bits in index. (#4601) * exp/lighthorizon: Add parameters to preload ledger cache. (#4615) * Add ability to preload cache in parallel after launching webserver * Default to 1 day of ledgers @ 6s each --------- Co-authored-by: Bartek Nowotarski <[email protected]> Co-authored-by: Paul Bellamy <[email protected]> Co-authored-by: Bartek <[email protected]> Co-authored-by: Bartek <[email protected]> Co-authored-by: tamirms <[email protected]> Co-authored-by: George <[email protected]> Co-authored-by: stfung77 <[email protected]> Co-authored-by: Leigh McCulloch <[email protected]> Co-authored-by: Alfonso Acosta <[email protected]> Co-authored-by: Alfonso Acosta <[email protected]> Co-authored-by: Graydon Hoare <[email protected]> Co-authored-by: Satyam Zode <[email protected]> Co-authored-by: Satyam Zode <[email protected]> Co-authored-by: erika-sdf <[email protected]> Co-authored-by: iateadonut <[email protected]> Co-authored-by: Shawn Reuland <[email protected]> Co-authored-by: shawn <[email protected]> Co-authored-by: Shivendra Mishra <[email protected]> Co-authored-by: Jacek Nykis <[email protected]> Co-authored-by: jacekn <[email protected]> Co-authored-by: George Kudrayvtsev <[email protected]>
PR Checklist
PR Structure
otherwise).
services/friendbot, orallordocif the changes are broad or impact manypackages.
Thoroughness
.mdfiles, etc... affected by this change). Take a look in the
docsfolder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
Enable the ledgerexporter image to be deployed/run as service in container orchestration, enable more env settings for configurability between testnet/pubnet. Create deployment on kubernetes that emits to S3 bucket.
Why
Will enable latest txmeta from network to be constantly exported to s3 buckets.
Known limitations