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

Update reusable-content-sync.yml #2463

Merged
merged 3 commits into from
Oct 11, 2024
Merged

Update reusable-content-sync.yml #2463

merged 3 commits into from
Oct 11, 2024

Conversation

ChrisMarsh82
Copy link
Collaborator

Defined secrets explicitly so can be passed from other organisations.
Removed Deployment Private Key as not used

defined secrets explicitly so can be passed from other organisations. 
Removed Deployment Private Key as not used
Copy link
Collaborator

@jfmcquade jfmcquade left a comment

Choose a reason for hiding this comment

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

Makes sense. I suppose there isn't a way to test that running from a different org's repo correctly passes in the secrets until after we've merged?

It could be worth keeping the DEPLOYMENT_PRIVATE_KEY as an optional secret (and using it to decrypt the config if it is supplied), as possibly in the future there could be a value from the encrypted deployment folder that is required for syncing content – e.g. a folder ID or URL that is considered sensitive. I can't really see an immediate use-case for that though, so happy to merge as-is.

@ChrisMarsh82 ChrisMarsh82 merged commit 3b3493c into master Oct 11, 2024
6 checks passed
@ChrisMarsh82 ChrisMarsh82 deleted the ChrisMarsh82-patch-1 branch October 11, 2024 14:11
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.

2 participants