Skip to main content
Version: Early Access

FluxCD Update Application

This workflow facilitates updating an existing application managed by FluxCD. It retrieves current application details and allows modification of its source and deployment manifests.

Application Verification​

The steps below identify the application to be updated and verify its existence.

Step 1: Application Input​

  • Task Type: User Input Task
  • Description: Specifies the application to be updated.
  • Properties:
    • FluxCD API Server: Reference to the fluxcd.APIServer CI.
    • Git Repository: Reference to the fluxcd.GitConfig CI.
    • Namespace: Namespace of the application to update.
    • Application Name: Name of the application to update.

Step 2: Check If Application Exists​

  • Task Type: FluxCD: Check If Application Exists
  • Description: Verifies the existence of the application.
  • Properties:
    • Server: The fluxcd.APIServer CI.
    • App Name: The name of the application.
    • Namespace: The namespace of the application.

Retrieve Application Information​

If the application exists, the following steps retrieve and parse the current application configuration.

Step 1: Get Application Information​

  • Task Type: FluxCD: Get Application Details
  • Description: Fetches the current source and deployment manifest details for the specified application from FluxCD and the Git repository.
  • Properties:
    • Server: The fluxcd.APIServer CI.
    • Application Name: Name of the application.
    • Namespace: Namespace of the application.

Step 2: Fill Application Information​

  • Task Type: Script Task
  • Description: Parses the fetched application details and populates release variables with current values (e.g., source URL, branch, chart version, paths). This provides context for the update.

Update Application Configuration​

These steps allow you to modify the application's source and deployment configuration.

Step 1: Application Source Information Input​

  • Task Type: User Input Task
  • Description: Displays current source manifest details and allows user to input new values for update.
  • Properties (Pre-filled and modifiable):
    • Source Manifest Name: Current or new filename for the source manifest.
    • Source Name: Name of the FluxCD source resource.
    • Source Kind: Kind of FluxCD source.
    • Source URL: URL of the source repository or chart.
    • Source Branch: Branch for the source.
    • Source Namespace: Namespace for the FluxCD source resource.
    • Source Rec Interval: Reconciliation interval.
    • Other source properties like Source Tag, Source Commit.

Step 2: Update Source Manifest​

  • Task Type: FluxCD: Update Source Manifest
  • Description: Updates the FluxCD source manifest in the Git repository with the new values.
  • Properties:
    • Git Repository: The fluxcd.GitConfig CI.
    • Server: The fluxcd.APIServer CI.
    • Manifest Filename: New or existing filename for the source manifest.
    • Old Manifest Filename: Original filename, if changed.
    • Other properties similar to FluxCD: Create Source Manifest.

Step 3: Kustomization Deployment Information Input (Conditional)​

  • Task Type: User Input Task
  • Description: Displays current Kustomization details and allows modification.
  • Properties (Pre-filled and modifiable):
    • Deployment Manifest Name: Filename for the Kustomization manifest.
    • Application Rec Interval: Reconciliation interval.
    • Path: Path for Kustomization.

Step 4: HelmRelease Deployment Information Input (Conditional)​

  • Task Type: User Input Task
  • Description: Displays current HelmRelease details and allows modification.
  • Properties (Pre-filled and modifiable):
    • Deployment Manifest Name: Filename for the HelmRelease manifest.
    • Application Rec Interval: Reconciliation interval.
    • Chart Name: Helm chart details.
    • Chart Version: Helm chart details.
    • Values Files: Helm values.
    • Values: Helm values.

Step 5: Create Deployment Manifest​

  • Task Type: FluxCD: Update Application Manifest
  • Description: Updates the FluxCD application manifest (Kustomization or HelmRelease) in the Git repository.
  • Properties:
    • Similar to FluxCD: Create Application Manifest, reflecting the new desired state, plus Old Manifest Filename.

Final Configuration and Monitoring Alignment​

The final steps confirm that the live deployment monitoring configuration is accurate post-update.

Step 1: Live Deployment Configuration Input​

  • Task Type: User Input Task
  • Description: Confirms or allows update of the associated live deployment configuration name in Release.
  • Properties:
    • Live Deployment Configuration Name: Name of the fluxcd.DeploymentConfig CI.

Step 2: Update Live Deployment Configuration​

  • Task Type: Script Task
  • Description: Ensures the fluxcd.DeploymentConfig CI in Digital.ai Release correctly reflects the updated application details if necessary.

Step 3: Setup FluxCD and Configure FluxCD​

  • Task Type: Script Task
  • Description: Re-applies or verifies FluxCD notification configurations for the possibly changed application definition.