floci-io/floci · error · AwsException

DeploymentConfigAlreadyExistsException

DeploymentConfigAlreadyExistsException

Error message

Deployment configuration already exists:  " + name

What it means

Error "Deployment configuration already exists: " + name" thrown in floci-io/floci.

Source

Thrown at src/main/java/io/github/hectorvent/floci/services/codedeploy/CodeDeployService.java:483

        if (groupStore == null) {
            return List.of();
        }
        return names.stream()
                .map(groupStore::get)
                .filter(g -> g != null)
                .collect(Collectors.toList());
    }

    // ---- Deployment Configs ----

    public DeploymentConfig createDeploymentConfig(String region, String name,
                                                    Map<String, Object> minimumHealthyHosts,
                                                    String computePlatform,
                                                    Map<String, Object> trafficRoutingConfig,
                                                    Map<String, Object> zonalConfig) {
        Map<String, DeploymentConfig> store = deploymentConfigsFor(region);
        if (store.containsKey(name)) {
            throw new AwsException("DeploymentConfigAlreadyExistsException",
                    "Deployment configuration already exists: " + name, 400);
        }
        if (name.startsWith("CodeDeployDefault.")) {
            throw new AwsException("InvalidDeploymentConfigNameException",
                    "Cannot create a deployment configuration starting with 'CodeDeployDefault.'", 400);
        }
        DeploymentConfig cfg = new DeploymentConfig();
        cfg.setDeploymentConfigId(UUID.randomUUID().toString());
        cfg.setDeploymentConfigName(name);
        cfg.setMinimumHealthyHosts(minimumHealthyHosts);
        cfg.setCreateTime(Instant.now().toEpochMilli() / 1000.0);
        cfg.setComputePlatform(computePlatform != null ? computePlatform : "Server");
        cfg.setTrafficRoutingConfig(trafficRoutingConfig);
        cfg.setZonalConfig(zonalConfig);
        store.put(name, cfg);
        persistRegion(deploymentConfigs, region);
        return cfg;
    }

View on GitHub (pinned to 62ff490619)

Solutions

  1. Choose a different deployment configuration name or delete the existing configuration first.

When it happens

Trigger: Thrown at src/main/java/io/github/hectorvent/floci/services/codedeploy/CodeDeployService.java:483 when the library encounters an invalid state.

Common situations: Occurs when creating a deployment configuration with a name already in use. Choose a unique deployment configuration name.


AI-assisted analysis of floci-io/floci@62ff490619 (2026-08-14). Data as JSON: /api/errors/41857daa0588bbb4. Report an issue: GitHub.