Issue 673 bigbang sso secrets
Package Owner Merge Request
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/673
Package Changes
What package changes are included with this merge request? The more detail here the better!
Links to all MRs that are associated with this change are required.
If the package is set up for releases, also link the package release page for the new tag here.
Additional Details
If possible, provide additional details that will help with the merge request.
Known issues or expected conflicts?
Also, include any issues closed with "Closes #ISSUE_NUMBER". See example:
Closes #ISSUE_NUMBER (paste the issue link for package issues, #ISSUE_NUMBER assumes BB issue)
Add any labels for affected packages so that they are deployed in CI. See example:
Once the MR is ready for review also add the status::review
label.
Merge request reports
Activity
added statusreview label
- Automatically resolved by Ronnie Webb
- Automatically resolved by Ronnie Webb
- Automatically resolved by Ronnie Webb
- Automatically resolved by Ronnie Webb
- Resolved by Ryan Garcia
- Automatically resolved by Ronnie Webb
- Automatically resolved by Ryan Garcia
removed statusreview label
added statusreview label
added 53 commits
-
146bfb7d...d494da88 - 46 commits from branch
master
- 3f7eb37b - issue 673 bigbang sso secrets
- edafeac8 - issue 673 change log modiications
- c0664ddc - issue 673 changing test to reflect changes
- 30addb66 - issue 673 changing test to reflect changes
- acdc71bd - issue 673 making changes per micah
- c7f21511 - issue 673 making changes per micah
- c0c17fd3 - issue 673 making changes per micah
Toggle commit list-
146bfb7d...d494da88 - 46 commits from branch
- Automatically resolved by Ronnie Webb
- Automatically resolved by Ronnie Webb
- Automatically resolved by Ronnie Webb
added statusdoing label and removed statusreview label
- Automatically resolved by Ronnie Webb
- Resolved by Ryan Garcia
@ronwebb After chatting with the integration team, I think it would be best to make the name for each of these secrets configurable via a value in
sso.secretName
? or a similar value.
- Automatically resolved by Ronnie Webb
Sorry @ronwebb testing these changes it looks like we will need to add a
twistlock.sso.enabled
value.We can add a comment above it calling out it's only for this secret creation and automatic SSO configuration for Twistlock is currently not available.
changed milestone to %1.17.0
removed statusdoing label
added statusreview label
mentioned in commit 49a8f023
mentioned in issue #634 (closed)
mentioned in issue #635 (closed)