refactor(cli): generalize cloud provider deployment - #203
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This refactors hosted deployment around a small cloud provider registry so future providers can plug into the existing CLI lifecycle without duplicating setup/update/resume/doctor/destroy commands.
AWS remains the only implemented provider for now, but its lifecycle, hosted Nango persistence, and agent sync readiness logic now live behind an AWS provider adapter. The CLI also gains
company-brain deployment targetto view or set the selected provider, stored separately from provider-specific config and inferred from existing AWS config for current installs.Railway-specific behavior is intentionally not included in this PR.