-
Notifications
You must be signed in to change notification settings - Fork 2
Add frodo config-manager export terms-and-conditions command #27
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
Conversation
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
e3de0a9 to
878126e
Compare
phalestrivir
left a comment
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.
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']; |
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.
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; |
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.
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(); |
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.
See previous comment, this should be const exportData = await readConfigEntity('selfservice.terms');
36e4d4e to
fe227fa
Compare
15fa910 to
8fe70e9
Compare
|
Everything in this PR should be in this one: #34 |
No description provided.