New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sch Agent resource updated to accommodate agent destroy resources #5691

Merged

hkantare merged 1 commit into IBM-Cloud:master from VaishnaviGopal:schematics

Oct 4, 2024

Collaborator

VaishnaviGopal commented Sep 30, 2024

ps: https://github.ibm.com/blueprint/product/issues/10856


          sch Agent resource updated to accommodate agent destroy resources

daed45f

VaishnaviGopal force-pushed the schematics branch from 3fd41c5 to daed45f Compare

September 30, 2024 07:54

Collaborator Author

VaishnaviGopal commented Sep 30, 2024

Agent deploy is applied

run_destroy_resources param value changed from 0-> 1 and hence when terrfaorm apply is done, a diff is found and hence it has gone to terraform update flow where run_destroy_resources job is performed to destroy agent deployment resources.

To test Agent destroy scenario, let us deploy the agent again and try using terraform destroy
Agent deploy is applied again this time using force parameter.

Agent PRS is performed to check if cluster has agent deployment(in this case, yes. Since we did agent deploy using force with terraform.)

Terraform destroy scenario:

First agent resources should get deleted and then agent itself should get deleted

hkantare approved these changes

View reviewed changes

hkantare merged commit f3b731b into IBM-Cloud:master

1 check passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet