You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got what looks like a bug with the RepositoryFile resource type. Initial creation of a resource works fine. However when I make changes to the value of the content field, the provider seems to get stuck in an endless reconciliation loop where it pushes empty commits nonstop and eventually blows through the rate limits on the API. I'm using the most recent version of the provider, v0.10.0.
Steps to reproduce:
# create a new RepositoryFile
$ kubectl apply -f - <<EOF
apiVersion: repo.github.upbound.io/v1alpha1
kind: RepositoryFile
metadata:
name: testfile
spec:
forProvider:
branch: main
content: |
foo: bar
file: test.yaml
overwriteOnCreate: true
repository: test-repo
providerConfigRef:
name: github
EOF
# wait for the provider to sync the file to the remote repo
# change the file contents
$ kubectl apply -f - <<EOF
apiVersion: repo.github.upbound.io/v1alpha1
kind: RepositoryFile
metadata:
name: testfile
spec:
forProvider:
branch: main
content: |
baz: qux
file: test.yaml
overwriteOnCreate: true
repository: test-repo
providerConfigRef:
name: github
EOF
# provider gets stuck in a reconcile loop
This results in duplicate commits in the repository:
I've got what looks like a bug with the
RepositoryFile
resource type. Initial creation of a resource works fine. However when I make changes to the value of thecontent
field, the provider seems to get stuck in an endless reconciliation loop where it pushes empty commits nonstop and eventually blows through the rate limits on the API. I'm using the most recent version of the provider,v0.10.0
.Steps to reproduce:
This results in duplicate commits in the repository:
Looking at the provider debug logs, seems like it applies the changes and then immediately requeues:
The text was updated successfully, but these errors were encountered: