feat(application): Webapp feature with production dns #167
No reviewers
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: NationTech/harmony#167
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/webappdns"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
2b105b280d
to528ee8a696
@ -58,2 +59,4 @@
}
// Returns true if any deployment in the given namespace matching the label selector
// has status.availableReplicas > 0 (or condition Available=True).
Should it be doc comments? Same question for the other functions below
@ -60,0 +135,4 @@
}
// Get the application-controller ServiceAccount name (fallback to default)
pub async fn get_argocd_controller_sa_name(&self, ns: &str) -> Result<String, Error> {
Does it have to be that specific? Or would it be ok if the signature was
Result<Option<String>, Error>
and that users of this function can decide what to do without values?For example:
@ -60,0 +172,4 @@
// Determine if Argo controller in ns has cluster-wide permissions via CRBs
// TODO This does not belong in the generic k8s client, should be refactored at some point
pub async fn is_argocd_cluster_wide(&self, ns: &str) -> Result<bool, Error> {
In addition to the comment above, I think it wouldn't be too tricky to refactor (if needed in another PR) with something like:
@ -22,3 +22,3 @@
pub version: Option<String>,
pub kube_version: Option<String>,
pub api_versions: Vec<String>,
// pub api_versions: Vec<String>,
still needed?
@ -194,7 +198,7 @@ impl<
openshift: true,
argo_apps: vec![ArgoApplication::from(CDApplicationConfig {
// helm pull oci://hub.nationtech.io/harmony/harmony-example-rust-webapp-chart --version 0.1.0
outdated comment -> to be removed
@ -0,0 +26,4 @@
InstalledNamespaceScoped(String),
}
pub async fn discover_argo_all(
a quick cleanup/refactoring for this function could make things easier to read/understand, for example by breaking down the different steps into different (module private) functions
Left a few comments here and there that could be small improvements for a future PR
Checkout
From your project repository, check out a new branch and test the changes.