-
Notifications
You must be signed in to change notification settings - Fork 398
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
Disable galaxy-importer docs tests #1270
Disable galaxy-importer docs tests #1270
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
2 similar comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
recheck |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 6m 00s (non-voting) |
Concept works, needs a change in the zuul job too |
Build failed (gate pipeline). For information on how to proceed, see Warning: |
regate |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 5m 42s (non-voting) |
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #1278 🤖 @patchback |
Backport to stable-4: 💚 backport PR created✅ Backport PR branch: Backported as #1279 🤖 @patchback |
Backport to stable-1.5: 💚 backport PR created✅ Backport PR branch: Backported as #1280 🤖 @patchback |
Backport to stable-2: 💚 backport PR created✅ Backport PR branch: Backported as #1281 🤖 @patchback |
Disable galaxy-importer docs tests SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION (cherry picked from commit 4435c8a)
Disable galaxy-importer docs tests SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION (cherry picked from commit 4435c8a)
Disable galaxy-importer docs tests SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION (cherry picked from commit 4435c8a)
Disable galaxy-importer docs tests SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION (cherry picked from commit 4435c8a)
[PR #1270/4435c8a6 backport][stable-3] Disable galaxy-importer docs tests This is a backport of PR #1270 as merged into main (4435c8a). SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
[PR #1270/4435c8a6 backport][stable-4] Disable galaxy-importer docs tests This is a backport of PR #1270 as merged into main (4435c8a). SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
[PR #1270/4435c8a6 backport][stable-2] Disable galaxy-importer docs tests This is a backport of PR #1270 as merged into main (4435c8a). SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
… tests (#1280) [PR #1270/4435c8a6 backport][stable-1.5] Disable galaxy-importer docs tests This is a backport of PR #1270 as merged into main (4435c8a). SUMMARY Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments. We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer ISSUE TYPE Feature Pull Request COMPONENT NAME tests/galaxy-importer.cfg ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
elbv2: respect UseExistingClientSecret SUMMARY Since amazon.aws 5.0.0, elb_application_lb runs into an exception, when using Type: authenticate-oidc in a rule, even when UseExistingClientSecret: True parameter is given. That works as expected with amazon.aws 4.x.x. The logic gets broken in ansible-collections#940 Basically AWS won't return both, UseExistingClientSecret and ClientSecret. But when requesting against boto3, both parameters are mutually exclusive! When the user set UseExistingClientSecret: True, the ClientSecret must be removed for the request. When the user does not set UseExistingClientSecret or set it to False, the UseExistingClientSecret must be included in the request. While diving deeper, I've noticed a basic change detection problem for default values, that are not requested, but AWS will return them. I've summerized it in ansible-collections#1284 However, this PR does not target ansible-collections#1284, it just fixes the exception and restores the functionality and hotfix the change-detection only for Type: authenticate-oidc. origin PR description The error was: botocore.errorfactory.InvalidLoadBalancerActionException: An error occurred (InvalidLoadBalancerAction) when calling the ModifyRule operation: You must either specify a client secret or set UseExistingClientSecret to true UseExistingClientSecret is not respected anymore since a.a 5 Introduced in ansible-collections#940 Furthermore, AWS returns also Scope and SessionTimeout parameters that are filled with default values if not requested. 'Scope': 'openid', 'SessionTimeout': 604800, That make the module always returns a change, if they are not requested. This fix does not break backwards compatibility, because the values are already set by aws, when not requested yet. ISSUE TYPE Bugfix Pull Request COMPONENT NAME plugins/module_utils/elbv2.yml ADDITIONAL INFORMATION - Conditions: - Field: host-header Values: - some.tld - Field: path-pattern Values: - "/admin/*" Actions: - Type: authenticate-oidc Order: 1 AuthenticateOidcConfig: Issuer: https://login.microsoftonline.com/32rw-ewad53te-ef/v2.0 AuthorizationEndpoint: https://login.microsoftonline.com/324re-dafs6-6tw/oauth2/v2.0/authorize TokenEndpoint: https://login.microsoftonline.com/432535ez-rfes-32543ter/oauth2/v2.0/token UserInfoEndpoint: https://graph.microsoft.com/oidc/userinfo ClientId: fasgd-235463-fsgd-243 ClientSecret: "{{ lookup('onepassword', 'some cool secret', vault='some important vault') }}" SessionCookieName: AWSELBAuthSessionCookie OnUnauthenticatedRequest: authenticate UseExistingClientSecret: True - TargetGroupName: "{{ some_tg }}" Type: forward Order: 2 Reviewed-by: Alina Buzachis Reviewed-by: Mark Chappell
SUMMARY
Because galaxy-importer tests the collections in a sterile environment it can't read the shared amazon.aws fragments.
We're separately testing the docs more thoroughly using a github action, so we can disable the broken docs fragment testing via galaxy-importer
ISSUE TYPE
COMPONENT NAME
tests/galaxy-importer.cfg
ADDITIONAL INFORMATION