Kapil Thangavelu
Kapil Thangavelu
from tfdump it looks like the backend subnet is an unknown cty ref.
right now the matched stuff is a flat list, it doesn't really capture filter hierarchy, we can add the 'not', 'or', 'and' to the list easily, but the full hierarchy...
warehouse will use the explicit post metadata over the file metadata, which is what causes the divergence. also to be clear poetry is creating the wheel, and a poetry plugin...
fwiw, as a result of this issues the plugin currently requires twine to publish. also this seems worth fixing simply as a race condition around building wheels with poetry and...
that looks like a golang template not a valid policy, can you provide a valid custodian policy that triggers this?
Has-statement is our current implementation of this, re client side normalizing and filtering. It would be nice to have a clear set of use cases that your looking to achieve....
yeah we should probably check the moved block as well
its more of a logged warning and ignored block effectively in this context vs a hard error.
@ddn0 thanks for the updates and making a re2 stub package.
try generating for a single provider. `custodian schema --json aws > aws-schema.json` I suspect that it's the largeness of the overall schema with all providers that's causing issues. I'm looking...