search

crossplane-contrib / provider-upjet-aws

AWS Provider for Crossplane.
https://marketplace.upbound.io/providers/upbound/provider-family-aws/
Apache License 2.0
150 stars 128 forks source link

provider-aws does not support source: Filesystem #287

Open celalettin1286 opened 1 year ago

celalettin1286 commented 1 year ago

What problem are you facing?

I think below source code is already self explanatory. Official AWS Provider doesn't support source: Filesystem and as seen in the below reference it checks for Secret, IRSA, WebIdentity.

https://github.com/upbound/provider-aws/blob/main/apis/v1beta1/types.go#L175

This is blocker for migrating from deprecated providers since we have implemented injecting cloud creds from vault using Filesystem.

How could Official AWS Provider help solve your problem?

kkr2320 commented 7 months ago

Crossplane-Contrib provider support filesystem as source. I tested the latest release by adding Filesyatem as allowed source to the ProviderConfig CRD and it works . Is it bug that the CRD is not updated ?
we use vault inject and feed credentials using side car.

shuknk8s commented 6 months ago

The issue with using crossplane-contrib provider is that down the line if you attempt to latest API spec for provisioning resources , the composition/XR request will fail complaining about kind missing, per my conversation with Chris Haar , the filesystem support in latest api of ProviderConfig should be updated. Waiting on @haarchri to schedule the implementation

github-actions[bot] commented 3 months ago

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 stale. 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.

haarchri commented 3 months ago

/fresh

github-actions[bot] commented 2 days ago

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 stale. 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.