ignore_changes does not work for lifecycle repository_files

[pavel-trubitsyn]

Engineers want to edit kustomization.yaml directly in repo, but tf will override changes on next apply. I tried to use lifecycle with ignore_changes, but it looks like does not work.

lifecycle { ignore_changes = [ repository_files ] }

In my case, I want to bootstrap cluster without overriding kustomization.yaml. Also, i tried kustomization_override option, but it will override changes on next apply too.

Is it possible to ignore changes in kustomization.yaml?

[cablespaghetti]

Having the same issue. There has to be some way of bootstrapping once and ignoring changes from then on...

[lodotek]

➕ 1️⃣ same here.

[ycyr]

Any update on this issue ?

[xsvil]

Seems like it's still not fixed in the latest provider version. Any ETA?

[swade1987]

Hello @pavel-trubitsyn 👋

I hope all is well with you. I'm just contacting you as part of our initiative to ensure the quality and responsiveness of our project's issue tracking. Thank you for your previous contributions by reporting issues you've encountered; your engagement is invaluable to the health and progress of our project.

I've reviewed the issue you reported and noted that it involves using supported resources, which is great. However, I also noticed that there has been little activity on this issue lately. We understand that circumstances change and priorities shift, which may affect the urgency or relevance of an issue.

We're implementing a policy regarding inactive issues to keep our project's issue tracker effective and up-to-date. If there's no further activity on this issue within the next 3 weeks, we will mark it inactive and close it. This approach helps us maintain focus on current and actively pursued concerns, ensuring resources are well allocated.

That said, we are still very much interested in resolving the issue you've encountered. If the problem persists or if you have any new information that could help us address it, please don't hesitate to update the issue or comment. Your input could be crucial in finding a resolution. Alternatively, if the issue no longer affects you or has been resolved, let us know so we can close it with the right resolution.

We're here to support and work with you to overcome any challenges you face using our project. Your continued feedback and participation are essential to our community's success.

Thank you once again for your contribution. I look forward to your update and am here to assist with any further questions or issues you might have.

Best regards,

Steve

[swade1987]

Closing as duplicate of https://github.com/fluxcd/terraform-provider-flux/issues/477, the recommended approach is described in that issue.