Skip to content
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

Receive mock managed identities rp identity in CS #899

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

machi1990
Copy link
Collaborator

What this PR does

Receive mock managed identities rp identity in CS

Jira:
Link to demo recording:

Special notes for your reviewer

@@ -272,6 +280,10 @@ objects:
objectName: ${FPA_CERT_NAME}
objectType: secret
objectAlias: firstPartyApplicationCertificateBundle
- |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to approach it having a single SecretProviderClass with N secrets or N SecretProviderClass ? I see different approaches depending on the MR.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both approaches are valid but I opted for this because I see no difference in terms of configuration between the SecretProviderClass I needed for this purpose and the firstPartyApp one. I'll defer this question to @janboll @geoberle on how they see it.

@miguelsorianod
Copy link
Collaborator

Having a quick look the approach seems good to me.

I'll defer to someone from the lifecycle team to give the ok to the approach as it involves templating and such

@cgiradkar
Copy link
Collaborator

lgtm *

@janboll janboll merged commit 215ac7a into main Nov 28, 2024
21 of 25 checks passed
@janboll janboll deleted the receive-mi-mock-identity branch November 28, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants