Skip to content

Conversation

@cuppett
Copy link
Contributor

@cuppett cuppett commented Mar 27, 2021

Was found by @yasseur1007 that deletes initiated while the stack was still being followed would get dropped. Also, if a stack was deleted on the AWS side, no attempt to reconcile/recreate would be possible. This PR resolves both of those.

Also, created an example which makes a CloudFront CDN in the samples directory. Added that and made one, combined S3 example getting ready for clean inclusion in samples for OLM CSV.

cuppett and others added 3 commits March 27, 2021 17:15
…an state

Observed the following sequence:

1) Create long-running stack create
2) During CREATE_IN_PROGRESS, delete k8s Stack
3) Delete timestamps got added, no deleteStack call made to AWS
4) Stack completed
5) Operator stopped following, but left resource as CREATE_IN_PROGRESS

The problem was in updates being performed to an out-of-date object handle (in the follower). Now, it fetches a fresh object (cached) for the latest version we have. This will give it more opportunity to work itself out.

See also: https://github.com/cuppett/cloudformation-operator/pull/1#discussion_r601849772
…ted by hand in AWS

Signed-off-by: Stephen Cuppett <steve@cuppett.com>
@cuppett
Copy link
Contributor Author

cuppett commented Apr 7, 2021

@linki you'll probably want this one before creating a 0.9

@yasseur1007
Copy link

Tested the PR and it worked as expected 👍🏼

@linki you should definitively merge it.

Signed-off-by: Stephen Cuppett <steve@cuppett.com>
@linki linki self-assigned this Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants