Skip to content

flowey: fix saving secret vars #1417

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

Merged
merged 1 commit into from
May 27, 2025
Merged

flowey: fix saving secret vars #1417

merged 1 commit into from
May 27, 2025

Conversation

jstarks
Copy link
Member

@jstarks jstarks commented May 27, 2025

We are trying to write a non-JSON-formatted value to track that an env-var-sourced variable is secret. Fix this by writing null. Also add in some diagnostics and improve the in-memory variable representation to avoid so many allocations.

@jstarks jstarks requested a review from a team as a code owner May 27, 2025 19:16
@jstarks jstarks merged commit ced1562 into microsoft:main May 27, 2025
27 checks passed
@jstarks jstarks deleted the too_secret branch May 27, 2025 19:43
@jstarks jstarks added the backport_2505 Change should be backported to the release/2505 branch label May 27, 2025
benhillis pushed a commit to benhillis/openvmm that referenced this pull request May 27, 2025
We are trying to write a non-JSON-formatted value to track that an
env-var-sourced variable is secret. Fix this by writing `null`. Also add
in some diagnostics and improve the in-memory variable representation to
avoid so many allocations.
jstarks added a commit that referenced this pull request May 27, 2025
We are trying to write a non-JSON-formatted value to track that an
env-var-sourced variable is secret. Fix this by writing `null`. Also add
in some diagnostics and improve the in-memory variable representation to
avoid so many allocations.

Co-authored-by: John Starks <[email protected]>
@benhillis benhillis added the backported_2505 PR that has been backported to release/2505 label May 28, 2025
@benhillis
Copy link
Member

Backported in #1421

@benhillis benhillis removed the backport_2505 Change should be backported to the release/2505 branch label May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport_2505_approved backported_2505 PR that has been backported to release/2505
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants