Repository navigation
[minor] Common module implementation for SaaS Feature status persistence - #501
Merged
Merged
Conversation
remove separate mongodb_schemas
svt01
changed the title
svt01
marked this pull request as ready for review
October 22, 2026 12:01
Contributor
Author
REQUESTED stateCommand: IN_PROGRESS stateCommand: ACTIVE stateCommand: |
Contributor
Author
REQUESTED stateCommand: IN_PROGRESS stateCommand: DEACTIVATED stateCommand: |
Contributor
Author
|
Attaching the logs from the suite-dns job |
mnivedithaa
previously approved these changes
Oct 22, 2026
whitfiea
requested changes
Oct 23, 2026
whitfiea
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR provides the new command that allows us to write the allowlisting provisioning status in mongodb. It writes MAS feature status details to
mas_devopsmongodb database.Related Issues
https://jsw.ibm.com/browse/MASCORE-18566
https://jsw.ibm.com/browse/MASCORE-19592
How Has This Been Tested?
The end to end testing is performed by updating the
allow-listinsaas-envs.Based on the calls from CIS allowlisting provisioning module to write the status the calls are captured from
suite-dnsand subsequent mongodb updates are shown.REQUESTED
The allow_list was provisioned in
saas-envsand in subsequent run in thesuite-dns, we can see the invocation ofmas-devops-feature-status-updatecommand with the status asREQUESTEDand same getting persisted in the mongodbIN_PROGRESS
The invocation of command to mark the status as
IN_PROGRESSbased on the call for allow-list provisioningACTIVE
Depending on the response for the allow-list provisioning call, the status is set to success ie
ACTIVEand same can be seen in the mongodbSimilarly, following screenshots details out the transition from IN_PROGRESS to DEACTIVATED
The status is updated to IN_PROGRESS, before transitioning to Deactivate status
IN_PROGRESS
DEACTIVATED
The call from the ansible-devops for writing the status as deactivated and the mongodb update with the new status as
DEACTIVATEDcan be seen below