You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You must manually install the jmespath dependency on the Ansible controller before using this filter. This filter is built upon jmespath, and you can use the same syntax. For examples, see jmespath examples.
Third option would be to have the ability to swap out the base image I guess ?
What do you think is a reasonable solution ?
Am I missing something or am I trying to do the 'wrong things' ?
I might add that for me ansible/terraform provider here is the crutch to help me fill any voids as well as a means to be able to migrate to a more cloud-native approach with crossplane. Hence I think it would be valuable if it was possible to at least some how cater to all the strange corner case ...
Oh and as a work around for at least the jmespath I managed to open shell and install it (not a good solution i know)
The text was updated successfully, but these errors were encountered:
I suggest install jamespath using ansible and pip. That is the way I solved that problem. But it was cool if the image already have this basic packages.
What problem are you facing?
You must manually install the jmespath dependency on the Ansible controller before using this filter. This filter is built upon jmespath, and you can use the same syntax. For examples, see jmespath examples.
REF https://docs.ansible.com/ansible/latest/collections/community/general/docsite/filter_guide_selecting_json_data.html
How could Crossplane help solve your problem?
It would be nice if controller base image could include the necessary dependencies for this ?
Alternative would be to have the ability to add dependencies as needed ?
an other example would be 'Openstack' which requires the sdk avilable
in my case i want to upload to a bucket ... REF https://docs.ansible.com/ansible/latest/collections/openstack/cloud/object_container_module.html#ansible-collections-openstack-cloud-object-container-module
Third option would be to have the ability to swap out the base image I guess ?
What do you think is a reasonable solution ?
Am I missing something or am I trying to do the 'wrong things' ?
I might add that for me ansible/terraform provider here is the crutch to help me fill any voids as well as a means to be able to migrate to a more cloud-native approach with crossplane. Hence I think it would be valuable if it was possible to at least some how cater to all the strange corner case ...
Oh and as a work around for at least the jmespath I managed to open shell and install it (not a good solution i know)
The text was updated successfully, but these errors were encountered: