Skip to content
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.

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

[RDS DB Instance and maybe others] Tags do not update once set #1436

Closed
tbmetcalfe opened this issue Aug 19, 2022 · 7 comments · Fixed by #1895
Closed

[RDS DB Instance and maybe others] Tags do not update once set #1436

tbmetcalfe opened this issue Aug 19, 2022 · 7 comments · Fixed by #1895
Assignees
Labels
bug Something isn't working

Comments

@tbmetcalfe
Copy link

tbmetcalfe commented Aug 19, 2022

What happened?

When you provision an RDS instance, and then attempt to update the tags, the tags will exist in the manage resource forProvider, but it will not actually update the tags in AWS. This does not cause the database to be updated in any way (i.e. it's not even attempting to update).

If you look at the Cloudtrail API calls, you'll notice that tags are never included when updates are sent to AWS.

How can we reproduce it?

  1. Create an RDS instance with any tags you like.
  2. Update the list of tags
  3. Note that the new tags never exist on the RDS instance in AWS.

What environment did it happen in?

Crossplane version: 1.9.0
AWS Provider version: 0.29.0

  • Cloud provider or hardware configuration: AWS EKS
  • Kubernetes version (use kubectl version): v1.21.14-eks-18ef993
  • Kubernetes distribution (e.g. Tectonic, GKE, OpenShift): EKS
@tbmetcalfe tbmetcalfe added the bug Something isn't working label Aug 19, 2022
@chlunde
Copy link
Collaborator

chlunde commented Aug 23, 2022

I think we should fix this after #1378 to avoid conflicts

@chlunde chlunde self-assigned this Aug 23, 2022
@ricardomiguel-os
Copy link

There are other bugs reporting the same issue with tags update: #1284 #1093

@SlevinWasAlreadyTaken
Copy link

SlevinWasAlreadyTaken commented Mar 7, 2023

@chlunde Hello :)
The PR #1378 you mentioned stopped receiving updates then it froze this ticket and related ones.
Would you accept a fix for the update of tags aside it then?
Thanks

@MisterMX
Copy link
Collaborator

MisterMX commented Mar 7, 2023

Hey, there,
I currently don't have the time to work on #1378. I think it makes sense to foward with this issue instead.

@github-actions
Copy link

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Aug 22, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2023
@bjeevan-ib
Copy link

/fresh

@MisterMX
Copy link
Collaborator

Duplicate of #494

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants