pub async fn apply(
    svc: String,
    force: bool,
    region: &Region,
    conf: &Config,
    wait: bool,
    passed_version: Option<String>,
) -> Result<Option<UpgradeInfo>> {
    match region.reconciliationMode {
        ReconciliationMode::CrdOwned => apply_kubectl(&svc, force, region, conf, wait, passed_version).await,
    }
}
/// shipcat apply
///
/// This is the main entrypoint for cli upgrades of a service in a region.
/// It now only supports the shipcat controlled CRD upgrade.
/// Tiller support has been removed.
///
/// The design goals of this is to support:
/// - shipcat apply mysvc
/// - shipcat apply mysvc -t semver
/// In both non-rolling environments (preprod/prod), and rolling envs (complement).
///
/// To allow version-less apply in rolling environment, we have to verify with kube
/// what the current version is.
///
/// The preparatory sanity
///
/// This is entry point should be used by both the cli to apply, and reconcile.
/// It is also entirely responsible for sending webhooks on errors / successes.
/// As such, it's entirely responsible for not propagating random errors here with `?`
/// Every error cases is something that might need to be notified.
shipcat apply
This is the main entrypoint for cli upgrades of a service in a region.
It now only supports the shipcat controlled CRD upgrade.
Tiller support has been removed.

The design goals of this is to support:
shipcat apply mysvc
shipcat apply mysvc -t semver
In both non-rolling environments (preprod/prod), and rolling envs (complement).

To allow version-less apply in rolling environment, we have to verify with kube
what the current version is.

The preparatory sanity

This is entry point should be used by both the cli to apply, and reconcile.
It is also entirely responsible for sending webhooks on errors / successes.
As such, it's entirely responsible for not propagating random errors here with `?`
Every error cases is something that might need to be notified.
shipcat apply This is the main entrypoint for cli upgrades of a service in a region . It now only supports the shipcat controlled CRD upgrade . Tiller support has been removed . The design goals of this is to support : shipcat apply mysvc shipcat apply mysvc - t semver In both non - rolling environments ( preprod / prod ) and rolling envs ( complement ) . To allow version - less apply in rolling environment we have to verify with kube what the current version is . The preparatory sanity This is entry point should be used by both the cli to apply and reconcile . It is also entirely responsible for sending webhooks on errors / successes . As such it ' s entirely responsible for not propagating random errors here with ` ? ` Every error cases is something that might need to be notified .
pub async fn apply(
    svc: String,
    force: bool,
    region: &Region,
    conf: &Config,
    wait: bool,
    passed_version: Option<String>,
) -> Result<Option<UpgradeInfo>> {
    match region.reconciliationMode {
        ReconciliationMode::CrdOwned => apply_kubectl(&svc, force, region, conf, wait, passed_version).await,
    }
}
pub async fn apply ( svc : String , force : bool , region : & Region , conf : & Config , wait : bool , passed_version : Option < String > , ) -> Result < Option < UpgradeInfo > > { match region . reconciliationMode { ReconciliationMode :: CrdOwned => apply_kubectl ( & svc , force , region , conf , wait , passed_version ) . await , } }
shipcat apply
This is the main entrypoint for cli upgrades of a service in a region.
shipcat apply This is the main entrypoint for cli upgrades of a service in a region .
svc
String
force
bool
region
&Region
conf
&Config
wait
bool
passed_version
Option<String>
svc
String
force
bool
region
&Region
conf
&Config
wait
bool
passed_version
Option<String>