-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Make ready for data tagging #9833
base: main
Are you sure you want to change the base?
Make ready for data tagging #9833
Conversation
0509c42
to
c6b474b
Compare
The test
The test
The test
The test
|
This comment was marked as outdated.
This comment was marked as outdated.
4d38619
to
39c9833
Compare
This comment was marked as outdated.
This comment was marked as outdated.
39c9833
to
3e337d8
Compare
This comment was marked as outdated.
This comment was marked as outdated.
e9f08b1
to
c6dac04
Compare
017513e
to
9d501ca
Compare
9d501ca
to
b92bf34
Compare
796e253
to
8097e02
Compare
This comment was marked as outdated.
This comment was marked as outdated.
8097e02
to
1a0f9da
Compare
1a0f9da
to
fa70d42
Compare
fa70d42
to
487e794
Compare
487e794
to
73f19f8
Compare
Right now we have three bugfixes:
Further I had to disable three plugins due to bugs:
Whether the plugins/modules need changes or ansible-core needs fixes depends on the issue, we'll see what happens over time. The YAML callback issue also prevents the sanity tests from passing, since it's currently not possible to even import the YAML callback. |
…ble_type filter and ansible_type test.
73f19f8
to
b894dd0
Compare
SUMMARY
This adds ansible/ansible#84621 to CI to test whether it causes problems in CI.
Ref: https://forum.ansible.com/t/data-tagging-preview-and-testing/40759
Ref: https://forum.ansible.com/t/data-tagging-playground/39909
ISSUE TYPE
COMPONENT NAME
CI