Skip to content

Conversation

@doy-materialize
Copy link
Contributor

Motivation

make it easier to split up some of our logic here into separate controllers

Tips for reviewer

this shouldn't result in any functional changes, only moving code around

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@doy-materialize doy-materialize requested a review from a team as a code owner December 2, 2025 20:57
#[clap(long)]
aws_account_id: Option<String>,
#[clap(long)]
environmentd_iam_role_arn: Option<String>,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The refactor is fine, but it does remind me that we should we should be probalby have prefixed the flags with the cloud, iam_role_arn is pretty AWS specific, but being explicit that it's AWS would've been nice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, we should rethink a bunch of this config but that'll require more migration work

Copy link
Contributor

@jubrad jubrad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Very minor comments.

);
// the only way this can return an error is if we drop the writer,
// which we do not ever do, so unwrap is fine
store.wait_until_ready().await.unwrap();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit - probably viable to put use expect... expect("writer dropped")


#[derive(Clone, Deserialize, Default)]
#[serde(rename_all = "camelCase")]
pub struct DefaultCertificateSpecs {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be in orchestratord/src/tls.rs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants