-
Notifications
You must be signed in to change notification settings - Fork 187
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
[full-ci] Store settings via metadata #3232
Conversation
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
💥 Acceptance test localApiTests-apiSpaces-ocis failed. Further test are cancelled... |
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
3048563
to
a873fdc
Compare
Signed-off-by: jkoberg <[email protected]>
1962eeb
to
7fcf6f5
Compare
Signed-off-by: jkoberg <[email protected]>
af5c9f5
to
f642801
Compare
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
Signed-off-by: jkoberg <[email protected]>
fa8364b
to
1a9d446
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.
@wkloucek Creating users works fine for me. Currently it is necessary to set |
Yeah, it doesn't work on my machine either. I can login but I can't access the settings/accounts UI.
Started oCIS like this: |
@C0rby this is happening when the settings folder could not be created properly. Could you remove |
Starting with a clean storage and the |
Ok cool thanks 👍 Imho it is acceptable to have to remove Should we do something about the |
Signed-off-by: jkoberg <[email protected]>
e8c251b
to
2d4d90a
Compare
Metadata: config.Metadata{ | ||
GatewayAddress: "127.0.0.1:9142", | ||
StorageAddress: "127.0.0.1:9215", | ||
ServiceUserID: "ddc2004c-0977-11eb-9d3f-a793888cd0f8", |
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.
should we really use the admin user here? why can't we use a system user like for the accounts service (95cb8724-03b2-11eb-a0a6-c33ef8ef53ad)?
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.
The service user wasn't working properly before as it was creating 10k files on a simple acceptance test. It seems to be fixed though. Let's see what the pipeline says...
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.
Well. Seems like it still doesn't work 😞
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.
@wkloucek I found a way around it. Can you check again?
Adding and removing it again with each ListAccounts() call was a huge overhead. This is a temporary workaround, the whole service is gonna be replaced by the idm service soon anyway.
Signed-off-by: jkoberg <[email protected]>
6eeed53
to
b7c934b
Compare
Signed-off-by: jkoberg <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
Description
Encourages settings service to store its data via the metadata service
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: