-
Notifications
You must be signed in to change notification settings - Fork 6
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
Platform 533 - Edit Forms in Puente Collect #472
base: master
Are you sure you want to change the base?
Platform 533 - Edit Forms in Puente Collect #472
Conversation
update James' master
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Google API Key | 03549bb | app.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
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.
@jamesgiegerich94 do you know how to implement a cloud-code function?
postIdentificationForm(postParams).then((surveyee) => { | ||
setSurveyee(surveyee); | ||
submitAction(); | ||
}, () => { | ||
// perhaps an alert to let the user know there was an error | ||
setSubmitting(false); | ||
// setSubmissionError(true); | ||
}); |
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.
@jamesgiegerich94 this is where we use the updateObject function
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.
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.
@hopetambala I didn't know how, but Joey got me going in the right direction
update my fork 2/23/23
Description of proposed changes
What does this pull request accomplish? Why should it be integrated?
Checklist
Put an
x
in the boxes that apply.Additional comments
Is there anything else you want us to know?