Skip to content

Conversation

@devintrivir
Copy link

No description provided.

cparkertrivir and others added 6 commits January 10, 2025 14:50
config-manager theme export feature added
config-manager services export feature WIP
config-manager scripts export feature added
config-manager mappings export feature added
added service provider export command
@devintrivir devintrivir requested a review from phalestrivir May 30, 2025 18:09
@devintrivir devintrivir force-pushed the feature/config-manager-terms branch from e3de0a9 to 878126e Compare May 30, 2025 18:29
Copy link
Collaborator

@phalestrivir phalestrivir left a comment

Choose a reason for hiding this comment

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

You will want to add tests for the new commands. You will need one e2e test, and you will need a few client_cli tests.

import { printMessage, verboseMessage } from '../../utils/Console';
import { FrodoCommand } from '../FrodoCommand';

const deploymentTypes = ['cloud', 'forgeops'];
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 know if fr config manager can work with ForgeOps? I don't think it does because service accounts don't exist in ForgeOps deployments and I don't see anything indicating ForgeOps is supported in their documentation.

If ForgeOps isn't supported, this should just include 'cloud' and no other deployment types.

import { extractFrConfigDataToFile } from '../utils/Config';
const {
exportTermsAndConditions,
} = frodo.terms;
Copy link
Collaborator

Choose a reason for hiding this comment

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

You will want to use this instead:

const { readConfigEntity } = frodo.idm;

I think that's the import for it. You can read the terms and conditions directly this way without needing your own custom implementation (see my review for the Frodo-Lib PR). The entity id you would pass into it would be selfservice.terms

*/
export async function exportTermsAndConditionsToFiles(): Promise<boolean> {
try {
const exportData = await exportTermsAndConditions();
Copy link
Collaborator

Choose a reason for hiding this comment

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

See previous comment, this should be const exportData = await readConfigEntity('selfservice.terms');

@phalestrivir phalestrivir changed the base branch from trivir to main June 5, 2025 19:36
@skootrivir skootrivir changed the base branch from main to config-manager June 17, 2025 18:37
@skootrivir skootrivir force-pushed the feature/config-manager-terms branch from 36e4d4e to fe227fa Compare June 17, 2025 21:44
@phalestrivir
Copy link
Collaborator

Everything in this PR should be in this one: #34

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.

5 participants