We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While using this command:
flux diff kustomization apps --path apps/dev
I get this error:
✗ failed to generate kustomization.yaml: failed to decode Kubernetes YAML from $HOME/$REPO/apps/dev/.sops.yaml: missing Resource metadata <nil> <nil>
I tried to use --ignore-paths with various patterns including: .sops.yaml **/.sops.yaml $PWD/apps/dev/.sops.yaml
But none of those worked. I was able to accomplish my task by deleting the .sops.yaml file then restoring it via git afterwards.
Create a kustomization in a standard format, and include a .sops.yaml which should be normally ignored, and it doesn't.
The file should be ignored and the diff should work.
No response
macOS 14.4.1
2.2.3, 2.3
N/a
The text was updated successfully, but these errors were encountered:
I have exactly the same problem. No matter how I exclude the files that I want excluded, they are not ignored.
Sorry, something went wrong.
Hey @matheuscscp could you please look into this? Thanks
No branches or pull requests
Describe the bug
While using this command:
I get this error:
I tried to use --ignore-paths with various patterns including:
.sops.yaml
**/.sops.yaml
$PWD/apps/dev/.sops.yaml
But none of those worked. I was able to accomplish my task by deleting the .sops.yaml file then restoring it via git afterwards.
Steps to reproduce
Create a kustomization in a standard format, and include a .sops.yaml which should be normally ignored, and it doesn't.
Expected behavior
The file should be ignored and the diff should work.
Screenshots and recordings
No response
OS / Distro
macOS 14.4.1
Flux version
2.2.3, 2.3
Flux check
N/a
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: