-
Notifications
You must be signed in to change notification settings - Fork 157
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
fix: Properly represent multiple versions of the same custom resource #516
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests, rebase and signed commit please.
2f33a3f
to
2c3f328
Compare
@dark0dave Sonar is flagging a couple of code smells...I am not sure that the suggested changes help the style of the tests in any way, but if you want me to make them I can |
2c3f328
to
c954f76
Compare
This PR has not seen any activity in last 60 days and has been marked as stale |
Signed-off-by: Andy Zawada <atzawada@gmail.com>
Signed-off-by: Andy Zawada <atzawada@gmail.com>
Signed-off-by: Andy Zawada <atzawada@gmail.com>
c954f76
to
321d972
Compare
Looks like you'll need to format this. |
This PR has not seen any activity in last 60 days and has been marked as stale |
This PR was closed because it has been stalled for 90 days with no activity. |
@atzawada this is some functionality I need so I am running your fork -- are you by chance able to get this formatted so it can be merged? 🙏 |
I took a quick peek into the issue #515 that I opened earlier. Looks like it was an issue with how the Rego template was being rendered for additional custom resources. Simply combined the resource versions in the go code before passing it all off to the template.
If this approach is deemed ok, I will go back and write up some additional testing around this.