-
Notifications
You must be signed in to change notification settings - Fork 132
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
[Elastic Cache Parameter Group] Parameter group not creating resources if "external-name" is set (0.44) #1005
Comments
Any update? |
Hi @WolfGanGeRTech, Could not reproduce with provider version
|
Hello, I have tested again with 0.47.1 and same issue. The manifest I used was: apiVersion: elasticache.aws.upbound.io/v1beta1
kind: ParameterGroup
metadata:
annotations:
crossplane.io/external-name: cache-params9
name: cache-params9
spec:
deletionPolicy: Orphan
forProvider:
family: redis7
name: cache-params9
region: eu-central-1 When I describe the resource I get:
Since he can't find the resource he should create one. |
@turkenf could you let me know which crossplane version you used? I am using: Crossplane Version: 1.12.2 |
@WolfGanGeRTech, thank you for your patience and responses here. I think there was a misunderstanding here, I could not reproduce the issue since I tested it on the main branch on my first attempt. Currently, I can reproduce the issue in However, the issue could not be reproducible in provider version |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
This issue is being closed since there has been no activity for 14 days since marking it as |
Bump We upgraded to: Crossplane: 1.16 But we are still facing the same issue, always need to add the "crossplane.io/external-name" after creating the ParameterGroup. |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
What happened?
The ParameterGroup.elasticache.aws.upbound.io/v1beta1 is not able to create new resources if "external-name" annotation is set.
It should first check if the resource exists and if not, create it, but when "external-name" is set he only tries to check if it exists and fails if it doesn't. The error returned is:
How can we reproduce it?
Just use this manifest and the error will occour.
What environment did it happen in?
The text was updated successfully, but these errors were encountered: