-
Notifications
You must be signed in to change notification settings - Fork 372
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
S3 is not generating data inside secret when parameter policy is defined (v0.38.0) #1747
Comments
Same happens to me, can someone take a look? |
could you try |
Hello, I tested again to check the events: Manifest used:
It did not generate any content inside the secret "issue1747" and the output was:
|
Any idea what might be happening? |
it looks like that your bucket is not ready and constantly updating |
I have the same issue with the bucket constantly reconciling and never reaching ready state. This only happens when policy is included in the bucket manifest. Version
The remote resource in AWS management policy seems to be correctly defined, could the provider think there's a difference between the manifest and remote spec when in fact they are equivalent? Manifest
Bucket Policy in AWS
|
Same with v0.40.0 ? |
I think the issue is related with #1758 , so it should be fixed after the release. PS: same happens with 0.40.0 |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
What happened?
After upgrading from v0.37.1 to 0.38.0 the S3 Bucket resource stopped outputting "Endpoint" and "Region" in the secret generated after creation.
I have used the example provided in the "examples" folder and it didn't output the values inside the secret. After performing a few tests I have identified that this only happens if parameter "policy" (new parameter introduced in 0.38.0) is defined.
How can we reproduce it?
Here are the files used for testing:
Not working example:
Working example
What environment did it happen in?
Crossplane version: v1.11.3
Crossplane AWS provider: 0.38.0
The text was updated successfully, but these errors were encountered: