1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Glue doesn't store it because if it would be saved with the job and would be leaked.
Eventually those credentials should be stored on AWS Secret Manager and just reference that secret in the job.
What you can do at the time being (other than having them at hand to copy/paste) is having a script that uses the API to execute the same action, you could have the script at hand in your computer and execute it as needed.
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/glue/client/update_source_control_from_job.html
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/glue/client/update_job_from_source_control.html
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
Thank you, this is a workable solution.
I have tested both functions. The update_source_control_from_job function works perfectly, however, the update_job_from_source_control function keeps on failing (even when making standard changes like the one in this post: https://aws.amazon.com/blogs/big-data/code-versioning-using-aws-glue-studio-and-github/). The error I received is: "Unable to fetch the HEAD commit from your Github repository.".