-
Notifications
You must be signed in to change notification settings - Fork 81
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
CLOUDP-209691: Added OIDC and AWS IAM auth fields for AtlasDatabaseUser #1221
Conversation
bdcc22f
to
3ce3a0f
Compare
Tests will be added today/tomorrow |
pkg/controller/atlasdatabaseuser/atlasdatabaseuser_controller.go
Outdated
Show resolved
Hide resolved
@igor-karpukhin I see no explicit logic for handling these new fields on the Atlas side of things. Presumable this is because these fields are transparently copied via |
internal/featureflags/featureflag.go
Outdated
featurePrefix = "FEATURE_" | ||
featureSeparator = "=" | ||
//nolint:stylecheck | ||
FeatureOIDC = "FEATURE_PREVIEW_OIDC_DB_ACCESS" |
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.
Is this the only known feature flag so far?
If so. How do we know we will need this feature flags going forward for more values?
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.
Actually this could be what we need if we go for a more controlled process for releasing features. Instead of a commit releasing a new feature or behaviour directly, a flag might control whether some of those are active and maybe even depend on what version value it is being built, the default feature flag value is different. One single codebase can release different operator versions without branching.
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.
Yes, this is the only feature flag so far. I implemented then as env variables as it is easier to configure for the k8s Deployment
and/or Pod
resource. We can also add flag processing if needed (e.g. --features=featureA,featureB
.
LGTM but waiting for other comments to be revisited and the tests to pass |
That's right. These values are just sent as is, without any processing. |
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.
lgtm modulo failing tests, great work! 🎉
pkg/controller/atlasdatabaseuser/atlasdatabaseuser_controller.go
Outdated
Show resolved
Hide resolved
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.
LGTM, love it, thank you for the patience! 🙏
cf26f10
to
ca4046a
Compare
Seems it needs a rebase |
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.
LGTM, just needs a rebase it seems
2eb9b66
to
a30b7de
Compare
2b6c94e
to
e16ef3f
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.
Still LGTM 👍
All Submissions:
Added OIDC and AWS IAM auth fields for AtlasDatabaseUser
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if there is one).