Disable Resyncing the desired state

[Dylan-KW]

Is your feature request related to a problem?
In some cases, i need not to resync resources state with the actual resource. i only need to create or destroy the aws resource with my custom resources.
i mean blocking resync, not only when after resync period but also restarting the controller

Describe the solution you'd like
with a controller option, --disable-block-resync(?), and corresponding annotation could be easily make this works.

Describe alternatives you've considered

[a-hilaly]

@Dylan-KW would a read-only mode help achieve what you're trying to do? checkout #2008

[Dylan-KW]

@Dylan-KW would a read-only mode help achieve what you're trying to do? checkout #2008

What I’m trying to do is like below

• Create the backing resource on aws resource when I create a ACK custom resource.
• Delete the backing resource on aws resource when I delete a ACK custom resource.
• Modification on ack custom resource are not pushed to the backing aws resource.
• Modification on backing resource are not re-synced with ack custom resource.

[ack-bot]

Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

[ack-bot]

Stale issues rot after 60d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 60d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle rotten

[ack-bot]

Rotten issues close after 60d of inactivity.
Reopen the issue with /reopen.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/close

[ack-prow]

@ack-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 60d of inactivity.
Reopen the issue with /reopen.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[michaelhtm]

Hey @Dylan-KW
Seems like this has been resolved with read-only feature: https://aws-controllers-k8s.github.io/community/docs/user-docs/features/#readonlyresources

Create the backing resource on aws resource when I create a ACK custom resource.
Delete the backing resource on aws resource when I delete a ACK custom resource.
Modification on ack custom resource are not pushed to the backing aws resource.
Modification on backing resource are not re-synced with ack custom resource.

There difference with what you described here and the feature:

• You can't delete a resource that is in read-only.
• You can only annotate it as read-only once it is successfully created, or during the adoption of the resource.

Other than that, no updates are made until the annotation is removed.