FISH-6773 Delete Application Reference on a Deployment Group #6356
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
So far, deleting application reference was reliably working on instances, but not on a deployment group. When delete-application-ref was used with a deployment group as a target, it removed the reference from DAS, but it didn't undeploy the application from the instance. Consequent
create-application-ref
failed (because the app was installed, but DAS wasn't aware of it).This PR fixes behavior of
delete-application-ref
with target to deployment group, which undeploys the application also from all instances in the deployment groupTesting
Testing Performed
Basically, the idea is to deploy an application, leave it deployed on DAS and make it available/removed from a deployment group. It is possible to call
create-application-ref
anddelete-application-ref
repeatedly. Customer wanted to make accessible a new version, therefor the test uses two versions of the same application:Also, the original report mentioned, that instances are marked as "Need to restart" -- this doesn't happen anymore.
Testing Environment
OpenJDK 11, Linux