Skip to content

feat: Add config-manager push secrets#70

Open
dallinjsevy wants to merge 6 commits into
mainfrom
feature-config-manager-push-secrets
Open

feat: Add config-manager push secrets#70
dallinjsevy wants to merge 6 commits into
mainfrom
feature-config-manager-push-secrets

Conversation

@dallinjsevy

Copy link
Copy Markdown

No description provided.

@dallinjsevy dallinjsevy force-pushed the feature-config-manager-push-secrets branch 5 times, most recently from acb1967 to f169ae5 Compare March 25, 2026 21:54
@phalestrivir phalestrivir force-pushed the feature-config-manager-push-secrets branch from f169ae5 to e01e9f4 Compare March 30, 2026 17:50

@phalestrivir phalestrivir left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

See my comments below for the requested changes

);

program
.description('Import ESV secrets.')

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We are missing some flags:

-n, --name
-x, --prune

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Don't use client ESVs, delete this and instead use your own test secrets.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Don't use client ESVs, delete this and instead use your own test secrets.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Don't use client ESVs, delete this and instead use your own test secrets.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Don't use client ESVs, delete this and instead use your own test secrets.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Don't use client ESVs, delete this and instead use your own test secrets.


/*
// ForgeOps
FRODO_MOCK=record FRODO_NO_CACHE=1 FRODO_HOST=https://nightly.gcp.forgeops.com/am frodo config-manager push secrets -D test/e2e/exports/fr-config-manager/forgeops -m cloud

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This is not a ForgeOps test, but a cloud test, so make sure this comment reflects that. Also, we don't need to include the -m flag for cloud deployments (although it's fine to leave it in if you want to)

const importData = JSON.parse(readFile);
const singleSecretImport: SecretsExportInterface = {
secret: { [importData._id]: importData },
};

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

In addition to supporting the flags I mentioned previously, we'll need to have support like we are doing for ESV variables to provide ENV that sets the variables before attempting to import them.

@dallinjsevy dallinjsevy marked this pull request as draft March 31, 2026 21:13
@dallinjsevy dallinjsevy force-pushed the feature-config-manager-push-secrets branch from e01e9f4 to 086d9ef Compare June 10, 2026 16:34
@dallinjsevy dallinjsevy marked this pull request as ready for review June 16, 2026 16:47
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.

3 participants