-
Notifications
You must be signed in to change notification settings - Fork 5
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
checking kubernetes:yaml:ConfigGroup
resources
#298
Comments
Hello @errordeveloper thanks for opening this. Could you share the output of Odd...I would expect For posterity: |
Thanks for getting back to me @RobbieMcKinstry! I've made a few changes and use load manifests dirctly from files instead of using a package.
So now there also Here is relevant policy logic:
I also added one
I'm trying to write policy logic for this also, and it seems like I'm hitting another bump, probably to do with that the resource is defoined in the promise callback... What happens is that I guess this leave me wondering wheather I'm really hitting the limitations of how policy is implemented at the moment? |
I am creating a GKE cluser and using
kubernetes:yaml:ConfigGroup
to deploy some workload to the cluster.Before I create any resources at all, my policy that looks for certain specific resources doesn't work, albeit it does later on, if cluster was already deployed.
So, in other words, when preview output look like this, it doesn't work:
But it works when the
kubernetes:yaml:ConfigGroup
resource has dependents in the preview output:It will take some effort to make all of the code sharable, but here is what the policy definition looks like at the moment:
It would make some sense if I could at least get the group resource itself, which I'm attempting to this way:
But it doesn't seem to be present at all.
The text was updated successfully, but these errors were encountered: