Skip to content
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

Follow-up to #5334 #5382

Merged
merged 3 commits into from
Jun 28, 2022
Merged

Follow-up to #5334 #5382

merged 3 commits into from
Jun 28, 2022

Conversation

jtcohen6
Copy link
Contributor

This PR:

  • Updates changelog entry from Update context README #5334
  • Adds annotation to render_value method (reimplemented for SecretRenderer)
  • Adds functional test case

I'll backport to 1.1.latest + 1.0.latest after merging. The test case requires a teensy bit of modification to work in v1.0 (old testing framework), but it passes for me locally there as well.

@jtcohen6 jtcohen6 requested review from a team as code owners June 16, 2022 10:00
@cla-bot cla-bot bot added the cla:yes label Jun 16, 2022
@github-actions
Copy link
Contributor

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

Copy link
Member

@emmyoop emmyoop left a comment

Choose a reason for hiding this comment

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

Just a small suggestion for the file name.

@@ -1,5 +1,5 @@
kind: Under the Hood
body: Update context readme + clean up context code"
kind: Security
Copy link
Member

Choose a reason for hiding this comment

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

nit: This won't change how the changelog markdown gets generated but for consistency can we change the file name to be Security-20220606-230353.yaml? For context, the filenames are just like this for uniqueness, they don't actually get any fields out of the name.

@@ -14,6 +14,7 @@ kinds:
- label: Docs
- label: Under the Hood
- label: Dependencies
- label: Security
Copy link
Member

Choose a reason for hiding this comment

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

🥳

@jtcohen6 jtcohen6 merged commit d5608dc into main Jun 28, 2022
@jtcohen6 jtcohen6 deleted the jerco/secret-rendering-follow-up branch June 28, 2022 08:06
@github-actions
Copy link
Contributor

The backport to 1.1.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.1.latest 1.1.latest
# Navigate to the new working tree
cd .worktrees/backport-1.1.latest
# Create a new branch
git switch --create backport-5382-to-1.1.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d5608dca322c63f1a894174b1f280ae55a217ab8
# Push it to GitHub
git push --set-upstream origin backport-5382-to-1.1.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.1.latest

Then, create a pull request where the base branch is 1.1.latest and the compare/head branch is backport-5382-to-1.1.latest.

jtcohen6 added a commit that referenced this pull request Jun 28, 2022
jtcohen6 added a commit that referenced this pull request Jun 28, 2022
jtcohen6 added a commit that referenced this pull request Jun 28, 2022
* Backport #5382 to 1.0.latest

* Rm changelog entry for previous change

* Satisfy old flake rules
jtcohen6 added a commit that referenced this pull request Jun 28, 2022
* Backport #5382 to 1.1.latest

* Rm changelog entry for previous change
agoblet pushed a commit to BigDataRepublic/dbt-core that referenced this pull request Sep 16, 2022
* Follow-up to secret rendering changes

* Update changelog entries

* PR feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants