-
Notifications
You must be signed in to change notification settings - Fork 13
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
ROX-14528: Add OCM mock client #761
Conversation
Skipping CI for Draft Pull Request. |
3eb3d43
to
e93ef82
Compare
e93ef82
to
f1a4657
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested it in my local env and it works, thanks!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SimonBaeumer, stehessel, vladbologa The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Build a mocked OCM client if
ocmConfig.MockEnable=true
. Change to the mocked OCM client as default for the development environment. The purpose of this change is enabling development without needing access to a real OCM service account.It seems some of the integration tests currently rely on the default being
OCM_ENV=development
, which up to now setocmConfig.MockEnable=false
. To compensate, integration tests now explicitly disable the OCM mock.The mocked OCM client returns a stubbed organisation upon request. It does not handle quota related endpoints, so it does not yet work in combination with
--quota-type=ams
. For this, more OCM endpoints would need to be stubbed in the mocked client.Supersedes #758
Checklist (Definition of Done)
Test manual
Documentation added if necessary (i.e. changes to dev setup, test execution, ...)ROX-12345: ...
Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.Test manual
Verified that local execution without ocm service account credentials works.