Glenn Pratt

Just seconding that this rule is inverted to my expectations as well. Lazy evaluation feels like the more surprising mistake. Double quotes evaluating now is not surprising in shell. 3.3k...

It'd also be neat if this could be defined on the CRD itself, perhaps an annotation.

I thought I mentioned extra vars or perhaps I don't understand. I'm looking at this from the perspective of a collection author. IIUC extra vars: - Can't have a common...

> Extra vars can have a common default, either provided in the extra vars or in the playbook (just need to use the Jinja2 `default` filter). > > They also...

> They also can be dynamic, for example, the extra vars could use `lookup` plugins. Yes, I can write custom lookup plugins - that's what I'm doing for now.

That's mostly from the perspective of a user, not a collection author. There are things I can't offer in a role that I can do with a playbook, but the...

This diff is just whitespace, I assume this was merged elsewhere?

If you'd like a monstrously terrible hack workaround: ``` {{- $now := now | unixEpoch -}} --- apiVersion: ansible.crossplane.io/v1alpha1 kind: ProviderConfig metadata: name: {{ $myName }} spec: credentials: - filename:...

@WintonHuang1893 ``` Resource temporarily unavailable fatal: unable to fork ``` That sounds like #304 which is fixed but not yet released. Restarting the deployment or deleting the pod would help...

I'm not sure if your p.s. was saying this, but you can use the V2 SDK alongside V1 (and we do with the AWS-Flow project I work on).