ApplicationSet which generates Applications with matching names should report an error and return about applicationset HOT 4 CLOSED

I'm willing to take a swing at this, unless Jonathan is already working on it.

from applicationset.

FWIW It's not a perfect example of the problem: I originally reproduced it when reviewing #45, but I can't exactly include an unmerged PR in the reproduction steps of another issue 😄 .

As for why 0 and not 1 (or 3), here's the design doc paragraph on that:

Applications Naming

Application names are required to be templated by the user and should be unique. The reasoning behind this is that ApplicationSets cannot reliably formulate a stable name which would be generated consistently when the ApplicationSpec changes. For example, we could not use the same technique utilized by ReplicaSets (which formulates the ReplicaSet name based on the hash of the pod template), because ReplicaSets are intended to be ephemeral whereas Applications are not.

Name conflicts within the same ApplicationSet are considered an error condition on the ApplicationSet. Name conflicts with existing applications would be an error or warning. To resolve this, ApplicationSets might also provide the ability to adopt existing applications.

from applicationset.

Why 0 and not 1? The first application to be created is perfectly fine

from applicationset.

OK, so when an appliactionset generates an application object then it should check for duplications and report an error

@jgwest do you want to raise a PR?

from applicationset.