Skip to content
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

Avoid conflict if two files have same base name #20

Open
itowlson opened this issue Dec 4, 2019 · 0 comments
Open

Avoid conflict if two files have same base name #20

itowlson opened this issue Dec 4, 2019 · 0 comments
Assignees

Comments

@itowlson
Copy link
Contributor

itowlson commented Dec 4, 2019

Not sure how we can do this, but if you have two files with the same (base) name e.g. foo.rego and policy/foo.rego and deploy both then they will end up overwriting each other's configmap, even if they have different contents.

Perhaps we should key the config map off the full relative file path (though this would be nasty for folks using the policy directory convention), or use the package/rule name, though this would be fiddly.

Anyway, the current 'tromple over each other' behaviour is not great.

@itowlson itowlson self-assigned this Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant